Hi Everyone
I have a Telstra HTC One XL which is unlocked, rooted and running Viper 3.2.7 - it has been working perfectly for a year.
On Friday it reported that the SD card was mounted read only - I did some forum searches and have tried mounting & scanning the SD card which didn't resolve anything. I have a backup of my data so thought that I'd wipe the device and upgrade to the latest ROM (v4.2.0)
However, the device is in permanent read only mode. I can (via Windows) apparently copy the ROM zip file to the device but it is never really there - disconnect the phone and re-connect and it's as if the copy had never happened.
I can also delete files but, after disconnecting and reconnecting, they're magically back
Deleting files via TWRP doesn't work either (same result)
Re-installing the old ROM (still on the SD card) doesn't happen either - the install says complete but even having told it to not keep my settings/data/programs everything is still there
I've tried sideloading the ROM update (says complete but actually isn't)
Wiping the system, caches etc via TWRP again reports as successful but isn't
I can't update TWRP, although it says OKAY
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery openrecovery-twrp-2.6.3.0-evita.img
sending 'recovery' (8176 KB)...
OKAY [ 1.030s]
writing 'recovery'...
OKAY [ 3.323s]
finished. total time: 4.368s
I can't manually update the boot.img, although again it says OKAY
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
sending 'boot' (6054 KB)...
OKAY [ 0.889s]
writing 'boot'...
OKAY [ 2.168s]
finished. total time: 3.073s
I've tried a couple of versions of fastboot as well.
Given that there's nothing I want on the phone and it's just not working correctly, I'm happy to do/try anything at all but have now run out of ideas - does anyone have any thoughts for me?
Many thanks in advance
David
tried to post in the venue area but got a pop up saying i had to post here. so, heres the situation.
i have a retail dell venue 7, i dont know the model as i cant boot in to it (thus the problem) i did "not" try to root the device, 1.5 years old, checked some messages, locked it, came back later, it wouldnt unlock, did a hard shut down, went to start it up and it just sits at the dell logo. so heres what ive tried so far.
1. if i power on i get a quick USB logo flash.
2. if i power on with usb cable hooked to pc the USB logo stays on the screen.
3. if i go in to droid boot and try recovery it reboots to the dell logo and just sits there.
im legally blind and am having a bit of trouble getting around here but ive tried the "IntelAndroid-FBRL-07-24-2015"
using the above, if i boot in to droid boot it shows up as "android phone" i have to install the adb driver each and every time (windows 8.1) i dont mind that. the above sees the tablet and even issues commands. the tablet reboots and i get a logo with a hat, but it goes no further. if i hold power up and connect to the pc it shows up as a "CloverviewPlus Device" under intel Soc.
this is what "IntelAndroid-FBRL-07-24-2015" shows when i try to do a "5 cwm" then a "T3"
***********************************************************************
FASTBOOT TETHERED RECOVERY LAUNCHER 07-24-2015
***********************************************************************
=======================================================================
DEVICE STATUS: FASTBOOT-ONLINE
DEVICE INFORMATION: DellVenue7000143194 fastboot
=======================================================================
copy needed files to our device
target reported max download size of 1322942464 bytes
sending '/tmp/recovery.zip' (3623 KB)...
OKAY [ 0.887s]
writing '/tmp/recovery.zip'...
OKAY [ 0.686s]
finished. total time: 1.573s
target reported max download size of 1322942464 bytes
sending '/tmp/recovery.launcher' (704 KB)...
OKAY [ 0.604s]
writing '/tmp/recovery.launcher'...
OKAY [ 0.686s]
finished. total time: 1.291s
target reported max download size of 1322942464 bytes
sending '/sbin/partlink' (349 KB)...
OKAY [ 0.571s]
writing '/sbin/partlink'...
OKAY [ 0.687s]
finished. total time: 1.259s
issue fastboot oem "stop_partitioning" command to start cwm recovery:
...
(bootloader) Stop partitioning
(bootloader) Stop partitioning
A
FAILED (unknown status code)
finished. total time: 0.635s
---------------------------------------
at which point the tablet reboots, but just sits there with that hat thing.
i dont care if i loose data, id just like to get this tablet back in working order. unfortunitly i have no idea how to do that. im comfortable with the command line but may need a bit of hand holding (i.e. step by steps, ive looked at the wiki but i cant figure it out sadly)
after digging through some emails and finding the service tag, i can now update this to say its a DELL venue 7 3770. and ive still had no luck.
so, i downloaded kernel.tar.gz from Venue_7_3730_CloverTrail_plus/ (yeah i fat fingered the model number above, my bad)
1st sign this wouldnt work? when i unzipped with 7zip i got an error about files all ready existing, not possible since it was an empty folder, but i went ahead any way. installed virtualbox, ubuntu, got that all set up. tried to run from in there and got a boat load of "read only" errors (even though other write/read tests worked fine)
so i figured, ok, lets just keep it "in the box" so to speak, made a folder with in ubuntu, redownloaded said file. used file manager to unpack it only to get an error about "no such file or directory" eh?
so i went over to terminal and tried to unzip it again, this time getting a "not a gunzip file" error, do what?
all of my googling seems to say im hosed any way as every thing i read says you need a good clean copy of /system from your "phone" (what , no one ever does this with a tablet?) to build the rom, kinda defeats the purpose of releasing the source dont it?
oh well, ive tried all i can try and with no one around here pointing me in the right direction, i guess i have a nice paper weight.
I'm sure theres no helping me, beings how im new to this, i run linux mint, not windows, and i made bad decisions to get here. i recently got a new moto g7 power with full intentions on using it as my guinea pig while i still had my old phone working. my plan was to not even install a sim card into my g7 until i had it properly rooted. i looked through all sorts of tutorials and tried many different things and learned alot along the way. long story short, ive been using the linux command line to do everything. i got my bootloader unlocked using the code that i requested from motorola. then i downloaded the 2 g7 ocean files, zip and img. i pushed the zip file into the /data/ folder, fastbooted from the .img file, got to twrp/ from there i went to advanced, install recovery Ramdisk, navigated to data, and selected the .img file. i tried this twice with no success, it would just boot normally and the twrp app wouldnt allow me to install the zip file, says its not rooted. so the last time i tried, i dont remember exactly how i did it but within the twrp recovery menu i found a way to boot slot b, but slot a was already selected by default. my thought was that i had installed the zip on slot b and not slot a. selected slot b, my phone shut off, and now nothing. just blank, wont even light a light, even if i plug it in.
i know that i shouldnt have been messing around with stuff i dont know much about, but hey, it beats watching the news right now, and that is why i didnt buy a 1000 dollar phone. also, i bought this phone from amazon prime, but im not sure id sleep good at night sending it back knowing i damaged it myself, however that was recommended to me. Thank you for any help/ info i may get.
Blank flash
jhomolac said:
I'm sure theres no helping me, beings how im new to this, i run linux mint, not windows, and i made bad decisions to get here. i recently got a new moto g7 power with full intentions on using it as my guinea pig while i still had my old phone working. my plan was to not even install a sim card into my g7 until i had it properly rooted. i looked through all sorts of tutorials and tried many different things and learned alot along the way. long story short, ive been using the linux command line to do everything. i got my bootloader unlocked using the code that i requested from motorola. then i downloaded the 2 g7 ocean files, zip and img. i pushed the zip file into the /data/ folder, fastbooted from the .img file, got to twrp/ from there i went to advanced, install recovery Ramdisk, navigated to data, and selected the .img file. i tried this twice with no success, it would just boot normally and the twrp app wouldnt allow me to install the zip file, says its not rooted. so the last time i tried, i dont remember exactly how i did it but within the twrp recovery menu i found a way to boot slot b, but slot a was already selected by default. my thought was that i had installed the zip on slot b and not slot a. selected slot b, my phone shut off, and now nothing. just blank, wont even light a light, even if i plug it in.
i know that i shouldnt have been messing around with stuff i dont know much about, but hey, it beats watching the news right now, and that is why i didnt buy a 1000 dollar phone. also, i bought this phone from amazon prime, but im not sure id sleep good at night sending it back knowing i damaged it myself, however that was recommended to me. Thank you for any help/ info i may get.
Click to expand...
Click to collapse
Most likely it's in Emergency download mode (EDL)
You will need a blankflash, several threads on this.
There's one here, that may work.
https://mirrors.lolinet.com/firmware/moto/ocean/blankflash/
Sent from my Moto E (4) using Tapatalk
EDL mode even though there is no sign of life whatsoever?
jhomolac said:
EDL mode even though there is no sign of life whatsoever?
Click to expand...
Click to collapse
There won't be anything on the phone, just a black screen, but it should show up on a PC's list of connected devices.
Sent from my Moto E (4) using Tapatalk
jhomolac said:
EDL mode even though there is no sign of life whatsoever?
Click to expand...
Click to collapse
Some phones will display a charge light some won't like he said it's in edl mode the PC sould display it and u should hear it make sound when u plugs the phone into PC on windows in not sure on Linux machine should b perty much the same on that aspect .One thing u might have to get different blank flashes for the different updates .If don't go the first time try again good luck
Thank you guys, i appreciate your time. sounds like i have to do some more research about flashing a motorola from linux. im somewhat new to linux as well.
jhomolac said:
Thank you guys, i appreciate your time. sounds like i have to do some more research about flashing a motorola from linux. im somewhat new to linux as well.
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/ocean/ here is a blank flash that should get u going dose the PC recognise ur phone when u plug it in if dose open terminal an PC type fastboot devices if it sees it your in luck I can typ fastboot boot (the name of ur recovery) if it boot into twrp then u might b able to switch it to a slot. There is comands for fastboot to switch but I don't know them
My computer does not notify me when I plug in my phone. But I don't remember it doing that even when I used it before.thank you.
You might need to charge the phone. With a blank/black screen it can appear off when it's not. Thus draining the phone completely. It widely suggested to charge phones to at least 80% before tweaking/rooting.
I will feel like a real dummy if that's the case. It is now on the factory supplies charger. Haha. Crossing my fingers. Thank you
If I use command lsusd in terminal, my phone pops up as a Qualcomm wireless router. Command fastboot devices brings up nothing
jhomolac said:
If I use command lsusd in terminal, my phone pops up as a Qualcomm wireless router. Command fastboot devices brings up nothing
Click to expand...
Click to collapse
It's in edl mode, use the blankflash
Sent from my Moto E (4) using Tapatalk
I've never done a blank flash before, I thought it was done by using: fastboot flash command. But it doesn't seem possible if: fastboot devices doesn't bring everything up. I am on linux by the way
jhomolac said:
I've never done a blank flash before, I thought it was done by using: fastboot flash command. But it doesn't seem possible if: fastboot devices doesn't bring everything up. I am on linux by the way
Click to expand...
Click to collapse
You need QPST to interface with EDL mode. I don't know if anything in here works on Linux, but it definitely works on Windows 10.
QPST Utilities
decided to give this another try. i have managed to get a little further, however this is where i am getting stuck. i wish i was more savy with this stuff. any chance anyone could help me with this?
also, is it nessecary to have an sd card in the device when i do this?
blankflash_from_QCO30.85-18]# /home/joel/Desktop/blankflash_from_QCO30.85-18/blank-flash.sh
< waiting for device >
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 0.005] ...cpu.id = 186 (0xba)
[ 0.005] ...cpu.sn = 2335135194 (0x8b2f55da)
[ 0.005] Opening singleimage
[ 0.005] Loading package
[ 0.013] ...filename = singleimage.pkg.xml
[ 0.018] Loading programmer
[ 0.019] ...filename = programmer.mbn
[ 0.019] Sending programmer
[ 0.318] Handling things over to programmer
[ 0.318] Identifying CPU version
[ 0.324] Waiting for firehose to get ready
[ 3.338] ...MSM8953 1.0
[ 3.338] Determining target secure state
[ 3.343] ...secure = yes
[ 3.387] Configuring device...
[ 3.394] Flashing GPT...
[ 3.394] Flashing partition with gpt.bin
[ 3.400] Initializing storage
[ 5.763] Target NAK!
[ 5.763] ...num_partition_sectors=61071360
[ 5.763] ...SECTOR_SIZE_IN_BYTES=512
[ 5.763] ...num_physical_partitions=3
[ 5.763] ...OEM_ID=74
[ 5.763] ...Product name=hB8aP>
[ 5.763] ...XML (0 bytes) not validated
[ 5.763] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
[ 5.763] Check qboot_log.txt for more details
[ 5.763] Total time: 5.763s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
sd_shadow said:
There won't be anything on the phone, just a black screen, but it should show up on a PC's list of connected devices.
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
What do I do if it doesn't?
I tried all the possible button combinations but still nothing.
uwucake2020 said:
What do I do if it doesn't?
I tried all the possible button combinations but still nothing.
Click to expand...
Click to collapse
Is there anything on the phone screen?
sd_shadow said:
Is there anything on the phone screen?
Click to expand...
Click to collapse
There isn't anything, and it doesn't seem to be in EDL mode. (I checked in the device manager)
uwucake2020 said:
There isn't anything, and it doesn't seem to be in EDL mode. (I checked in the device manager)
Click to expand...
Click to collapse
Spoiler: It may be hidden in Ports like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello,
I started to look for a way to move away from the big tech mosters and I've been on iPhones for a while (iPhone 11 Pro right now). I did develop for Android in the past, I am experienced developer and Linux admin so the technical side does not concern me too much. Long story short, I want to give Android another try but I want to be free of the unwanted baggage that comes with it.
Probably Nokia 8.3 was not the best pick but I consider it a strategic buy and the price was good. It is also somewhat nostalgic - I used to work at Nokia in the past, before the company got destroyed by you-know-who. So I would love to have something with their logo again
As far as I understand, currently there is no any alternative ROM available for this device. I was looking towards /e/OS or LineageOS, but probably it is too early. So, I am wondering what would be the best way to move forward with such a phone? So far my plan looks like this:
- unblock the bootloader immediately after receiving the phone, I would expect it to have Android 10 preinstalled and the "fix" seems to be available. I understand the risk but without the risk I will be the product, not the phone
- try to remove as much google as possible from the original system and move more or less to what I would have with LineageOS - MicroG and alternative apps
- wait for the official/beta support from one of these alternative ROMs and migrate
First, does it sound doable today? I found an excellent guide on this forum about "degoogling" the Android but it requires TWRP and it does not seem like it supports Nokia 8.3 yet.
I would really appreciate an advice on the best course of action.
Well, did not get too many answers, starting to write my own. I have received the toy today and had a bit of time to play with it. Happy to report that I went all the way through unlocking the device successfully and rooting it with Magisk. All by the book, no surprises. Maybe this will help someone:
- Started Nokia 8.3
- Accepted TOU
- Skipped all settings, offline
- verified it was running Android 10, Build number: 00WW_1_110 (00WW_1_110_B01)
- hardware: TA1243, product: lito, Variant: SM_ UFS
$ fastboot oem getversions
(bootloader) model=CaptainAmerica
(bootloader) sub_model=none
(bootloader) software version=00WW_1_110
(bootloader) SW model=
(bootloader) build number=A01
(bootloader) hardware version=A1-1
(bootloader) RF band id=
OKAY [ 0.001s]
Finished. Total time: 0.003s
$ fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
$ fastboot flash abl abl_proto.elf
Sending 'abl_a' (268 KB) OKAY [ 0.013s]
Writing 'abl_a' OKAY [ 0.003s]
Finished. Total time: 0.025s
$ fastboot flashing unlock_critical
FAILED (remote: 'unknown command')
fastboot: error: Command failed
$ fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
$ fastboot oem unlock-go
OKAY [ 0.045s]
Finished. Total time: 0.045s
Then I have connected WiFi network and OTA updated the device to 2_200 (Android 11)
Extracted boot.img from OTA zip using https://github.com/cyxx/extract_android_ota_payload.git
(used Python 3.8.3 and "pip install protobuf" before)
Followed https://topjohnwu.github.io/Magisk/install.html by the letter.
Patched boot.img with Magisk app, restarted into bootloader and flashed the modified boot image. Seems to be working
Next part - removing some software I do not want to see on this phone
I am with you
However, I used adb on host computer
Code:
adb reboot recovery
When you see dead bot, press both power + volume up buttons every 2 seconds to see actual recovery. You can choose adb sideload, and you can install ROM from host computer
Code:
adb sideload
Press spacebar once and drag and drop the ROM file to command window
Downgrade to 10 is still possible though you may see "downgrade not possible" (I flashed from 180 back to 150 in order to "patch" bootloader in order to unlock)
I successfully rooted mine and it looks like I am no longer abandoning it
TV streaming on Philo is no more hiccup
Headphones jack is capable up to 24bit/384kHz, but it's highly recommended to use USB C digital headphones adapter for maximum possible benefit
mingkee said:
I am with you
However, I used adb on host computer
Click to expand...
Click to collapse
I had old Android 10 preinstalled so I did not have to downgrade.
So far I am messing with the phone trying to minimize the data leaking while preserving the functionality I want. AFWall+ etc...So far seems OK. I also use Pi-Hole at home and planning to actually set up VPN on the device so it would be always connected to my home network. The only thing I am not sure about, I had to allow network access to Google Play Services, otherwise some apps would not work or behave in an odd way. For example, Waze worked with it disabled but Ring stops working minutes after logging in. I am wondering if allowing Google Play Services opens the floodgate of Google spyware. I am doing traffic analysis on the device, investigating who connects where. At the end I will write my "tutorial" on this. Personally I could not find one good tutorial about how to maximize your privacy with stock ROM and rooted phone.
Thanks for the tip about the audio!
Maybe you can run @AndyYan 's Lineage OS GSI on this phone.
When I discovered the unlock method, I've tried GSI already.
Here's the GSI test report I made for 8.3:
Nokia 8.3 5G
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
To flash GSI, you'll need to boot to Fastbootd:
Code:
adb reboot fastboot
Then flash GSI (bvS variant):
Code:
fastboot erase system
fastboot flash system /path/to/lineage-18.1-20210411-UNOFFICIAL-treble_arm64_bvS.img
fastboot --disable-verity --disable-verification flash vbmeta /path/to/vbmeta.img
fastboot -w reboot
Can't figure out how to get this to 100% factory settings and ROM? rSD doesn't recognize the devices, when I use tiny script it doesn't seem to reset it 100¹ to factory.
Anyway to "trick" RSD? Or any other step by step method I'm missing?
me too
hawki said:
Can't figure out how to get this to 100% factory settings and ROM? rSD doesn't recognize the devices, when I use tiny script it doesn't seem to reset it 100¹ to factory.
Anyway to "trick" RSD? Or any other step by step method I'm missing?
Click to expand...
Click to collapse
RSD lite doesn't work with Windows 10/9, use Windows 7
Hello,
You need the blankflash files to flash back to stock if you can't access fastboot mode.
I have the files for the G100 if you need them.
Hi,
I would totally love to have those blankflash files, my G100 just got hard bricked.
Hello,
I am attaching all the BlankFlash files here. As long as your phone shows up in device manager as a serial device then you can use these to fix it as I did mine. If it doesn't work hold power down until it blinks Device manager. I do require payment in the form of getting TWRP working though ;-)
@marcusah123 thank you!!
I 1st tried to run run the linux script a bunch of times but no luck..
[[email protected] blankflash_nio_RRTS31.Q1-84-24-3-6]$ doas ./blank-flash.sh
< waiting for device >
Motorola qboot utility version 3.86
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 0.002] ...cpu.id = 195 (0xc3)
[ 0.002] ...cpu.sn = 2312450350 (0x89d5312e)
[ 0.002] Opening singleimage
[ 0.002] Loading package
[ 0.006] ...filename = pkg.xml
[ 0.008] Loading programmer
[ 0.009] ...filename = programmer.elf
[ 0.009] Sending programmer
[ 0.166] Handling things over to programmer
[ 0.167] Identifying CPU version
[ 0.167] Waiting for firehose to get ready
[1470.626] Waiting for firehose to get ready
[1473.627] serial_write(), line 280: Input/output error
^CInterrupt
then gave up fired up another laptop that still has windows on it, and well the updates took longer than to get fastboot screen.
Thank you!
Glad that worked. Now how do we get TWRP working? It attempts to boot but causes a boot hang.