Related
Before I get into the gist of my current problem I think it might be relevant to provide some backstory. I decided I wanted to try and root my phone so I could install a new custom ROM. I had done some jailbreaking back when the iPod touches came out, back when jailbreaking was extremely ghetto and unreliable, so I figured I could teach myself this fairly easily. I unlocked bootloader using the htcdev method without an issue, and, following a guide, downloaded something called Rootboot to flash the phone. There was only one step to this portion, so I assumed it would be easy. Running the rootboot started rooting my phone, however after a couple of lines in the command prompt it said something about the adb, failed, and the phone was stuck in a boot loop with no roms on it at all. I stayed up all night with the damn thing attempting to fix it, and at one point, actually got it to load up the stock ROM from the computer using some combination of RUU's and fastboot commands. I have no clue how I did it, all I know is that it was not through adb sideload because the recovery I had at the time wouldn't work with adb sideload for whatever reason. It was the recovery that came with the All-In-One toolkit, for the AT&T / TELUS version. At this point I figured since the phone was working I would just install the VenomROM, and after a few hours of playing around with fastboot and the bootloader trying to get a ROM loaded, I figured I was familiar enough with all of them to load the ROM.
Which is what brings me to my current issue. I KNOW the boot.img is flashed to the device because I used the All-In-One Toolkit to do it, erased the cache, did it again using fastboot commands in the command prompt, erased the cache, and continued to use recovery to install the ROM. I got it to load and install, cleared the darvik cache, data, and cache, but when booting, the phone would get to the lock screen, upon which sliding to unlock, presented me with a white screen that says "htc" on it instead of a launcher. After a couple of seconds of waiting, it says, "setup has quit responding" and gives me the option to close or to wait. Either option results in the phone rebooting wherein I only see a black screen with the notification bar at the top displaying my battery and no internet/network connection. I have gone back and flashed the boot.img again and cleared cache, darvik cache, and data several times and just have no clue what I'm doing wrong to not get this phone to boot with the ROM. I can reflash at any point from my sideload.zip file and the installation process has an option to flash the kernel (boot.img) because it is included in the zip. Any help would be much appreciated. I highly doubt theres anything wrong with the ROM or boot.img, it is probably me just not doing it right.
I am using (or attempting to use) the 1.2.7 version of VenomXL+ on the HTC One X+ along with TWRP 2.5 as the recovery.
so i have been using multirom and reflashed a rom to my internal rom. then i rebooted it and it is stick with a blank screen after the "google" logo and stuck there. when i go to twrp, it prompts me for a password that i have not set. I have read that this happens if you dont reboot after unlocking but i did that when i first unlocked the bootloader and have never ran into any problems flashing many roms till now. any ideas???
onecrzyasian said:
so i have been using multirom and reflashed a rom to my internal rom. then i rebooted it and it is stick with a blank screen after the "google" logo and stuck there. when i go to twrp, it prompts me for a password that i have not set. I have read that this happens if you dont reboot after unlocking but i did that when i first unlocked the bootloader and have never ran into any problems flashing many roms till now. any ideas???
Click to expand...
Click to collapse
Did u try to wipe "format data" as explained by Dess_Troy?
This happened to me too when I flashed a kernel without making sure it was correct for the rom I was running. I just forced it to reboot into recovery and it turned out fine. Have you tried that?
Sent from my Nexus 5 using Tapatalk
If you have just used fastboot oem unlock, you should let the device boot up normally first before trying to install TWRP. If you boot TWRP first before booting normally, you will be prompted for a password. Hit cancel and got to Wipe -> Format Data. Type yes at the prompt and hit the "enter" key. Hit the home button at the bottom and Reboot -> Recovery. Unlocking the device will cause you to lose all userdata, apps, pictures, downloads, etc.
Click to expand...
Click to collapse
Source: http://www.teamw.in/project/twrp2/205
It'll be ok
This has happened to me a couple times, all I had to do was hit cancel and it went into recovery, no password needed. Just needed to reflash Multirom.
hmm wonder if i could have reflashed the multirom. cuz when i tried to reflash roms or try to flash another roms or anything, it wouldn't work. said the files were all encrypted. under the file manager, there was no accessible or viewable files. completely locked out. I ended up doing a back up by going into bootloader and pulling files to my desktop then did a stock flash.
as for the reformatting, i've shouldn't/wouldn't want to do that because i have already unlocked the bootloader, did the fastboot reboot and flashed countless roms and kernels. I think there was some sort of corruption that screwed with something. And i really didn't want to lose all my data be reformatting it.
only booting into recovery and clicking cancel when prompted password made me completely locked out. said that everything was encrypted so i was out of luck.
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
kozaqu said:
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
Click to expand...
Click to collapse
That got me in the right direction and I can at least get back into recovery now. Thanks! :good:
Also in the same boat
mkhopper said:
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Click to expand...
Click to collapse
I'm also sort of in the same boat i had a custom rom installed and decided to go back to stock os and now i'm stuck at either the Nvidia Logo or the Fastboot menu there's nothing else it let's me do i'd take any advice at this point. I can use Fastboot commands and I've tried Flashing Twrp.img and also flashing all the stock os which goes through with no problems i reboot the device and it's just stuck at the Nvidia logo
Ps: how did you manage to get back into recovery
Hello.
I think i had the same Problem.
I Flashed a Custom Rom, MiniGapps and the tegra...Battery file and since then i had boot loop an the NVidia Logo.
The Problem was: i flashed the tegra-Battery.ZIP file!!!
I noticed that i have to unzip it and flash teh tegra-..battery.DTP file.
since then it booted up again.
the OpenGappMini was buggy. it worked with the Nano!
Hope this helps for you as well!
OMG you guys. I did the exact same damn thing. Flashed the ZIP instead of the DTP file. 100 million thanks to you. I'm going to give it a shot now.
It worked! I wonder how many other folks didn't realize it wasn't a zip to flash to dtb and bricked their devices.
Hey everyone, I'm in a pickle with mi Ultra.
I'll walk you through the key events that led me to where I am now.
Yesterday, I noticed my battery was being used up fairly quickly, the battery settings showed that "other" had drained my battery 16% over the course of a few hours. I decided I wanted more info so I got recommended to try installing Gsam and it's root addon to see if I could get more details.
At this point in time, I was on EU rom with Magisk running smoothly, after installing Gsam and the root addon it wanted me to reboot, and so I did. That was the last time since then that I have been able to get in to my phone.
It started with a bootloop, so I tried unrooting via TWRP, wiping cache, nothing.
After a while i said **** it, if I lose my data so be it. Tried dirty flashing the EU rom again, no luck. And now I couldn't see /data no more in TWRP.
Decided to try a fresh install of EU rom, formatted data via TWRP and installed EU rom again, still no.
So then I tried following the guide I followed orginally to install the EU rom via my PC, nope again.
Maybe the china rom could help here? Tried installing it via fastboot command-line - nope, via sideload - nope, via MiFlash - no.
The loop has during these hours of terror behaved differently, but the farthest I've gotten is being able to type in my wifi Password to start trying to unlock my Mi account, but just after that, the touch becomes unresponsive and "System has stopped responding" and then reboot.
So, I turn to you guys for help, I've followed all guides/forum threads that I could find about bootloops and bricking on the ultra (including the ones here of course) but so far none of those tips have solved my problem.
Does anyone have any more things that I could try?
If need be I can post a video of the problem as it occurs.
Thanks in Advance, Chris
After any branch change flash, did you format? If not, it will boot loop. No good formatting before flashing, it must be done after. I would start again by going to fastboot and install the original stock Chinese ROM. This will replace twrp with stock recovery. Get a fastboot ROM from mifirm.net .
Once done, then check it's working Ok and build on that with flashing twrp from fastboot and then a twrp ROM. BUT after flashing any same branch ROM, you must wipe cache and dalvik. If you change branch like stock to EU or stable to weekly, you must format data as there may be different partition differences. It is very hard to brick an Xiaomi phone as you will always have access to fastboot. Just one word of advice, if you choose the first EU fastboot ROM, you need to swap out the fastboot.exe as it had an issue but other than that slow down take your time and it will work. Good luck.
Hi, i just got my old 5 year old (now retired) device to bootup because someone had made a kernel for the device which supports overclocking so for the fun I wanted to try it
but there was one weird problem, it seemed that though the root permissions from years ago remained just like they were but magisk manager itself had lost root permissions though I was still able to grant root permissions to other applications normally
I was on an unofficial Lineage OS build and thought of returning to original Miui for the device, got the fastboot rom, got Mi flash, flashed it, booted up
but there was a catch, it would always throw an error on the login Miui account screen at startup saying "Couldn't check device security, please try again"
I had tried everything possible including:
adding a Xiaomi account
skipping sign in
Inserting a sim
None of them seemed to do anything so i flashed twrp recovery again as using mi flash to flash ur device's stock rom gets rid of custom recovery
Now here is the mistake I made
**I wiped the device clean using TWRP**
now i tried going into adb sideload mode, no matter what I did my PC wouldn't detect my device, tried going into fastboot mode and still my PC wouldn't recognise the device and same goes for Mi flash tool
additionally the device would automatically exit out of fastboot mode within 2 minutes and go on to the power off screen
I do have charge on the device it says it's at 87% on the TWRP menu
I can no longer bootup, im stuck at the MI logo on bootup
Device: Mi Max 2
Additional notes: I am not in a hurry as that is not my primary device so it is okay if you want to take your time to reply, even if there's no way i can get my phone to see the light of day again it's alright as the phone was retired and sitting collecting dust for 2 years now
I do not wish to visit a service center as it's not worth it for a device I'm just gonna use for a few hours then put it back into its grave again
just download that same, or another custom ROM, and flash it via TWRP (just put ROM in SD card).
Nothing is gone, i mean if you delete system via twrp of course it will bootloop as it don't have system.
And for reverting back to original stock ROM , i think it have to do something with encryption, or maybe just the fact you unlocked bootloader.
Best is to stay away from stock ROM, find some custom ROM which have similar to MIUI (stock rom) , somewhat improved, if you want to get as much stock ROM experience.
kraken-gz said:
just download that same, or another custom ROM, and flash it via TWRP (just put ROM in SD card).
Nothing is gone, i mean if you delete system via twrp of course it will bootloop as it don't have system.
And for reverting back to original stock ROM , i think it have to do something with encryption, or maybe just the fact you unlocked bootloader.
Best is to stay away from stock ROM, find some custom ROM which have similar to MIUI (stock rom) , somewhat improved, if you want to get as much stock ROM experience.
Click to expand...
Click to collapse
Hi, thanks for the reply, I tried using an SD card and unfortunately it wouldn't detect that too, what i found was I didn't wipe System it still shows that it's taking up some place (3597 MB)
i would be fine getting a custom rom on the device infact i have crdroid ready to be installed
could it be that the TWRP i installed (yes I downloaded the latest version and didn't flash the old one i had years ago) have some bugs? (I did install it from official TWRP website)
also note: though you see a Senior Member title below my name, im a complete and utter noob
BR4UTAL said:
Hi, thanks for the reply, I tried using an SD card and unfortunately it wouldn't detect that too, what i found was I didn't wipe System it still shows that it's taking up some place (3597 MB)
i would be fine getting a custom rom on the device infact i have crdroid ready to be installed
could it be that the TWRP i installed (yes I downloaded the latest version and didn't flash the old one i had years ago) have some bugs? (I did install it from official TWRP website)
also note: though you see a Senior Member title below my name, im a complete and utter noob
Click to expand...
Click to collapse
Lol I thought I was the only proper noob here on xda but nice to meet other noobs here too .
I think Kraken-gz is right, once the older devices are OEM off-support its best to stay away from OEM servers, I lost couple of old lesser-known-brand devices to OEM mischief i'd say coz it happened twice to me when I reloaded the original ROMs and tried to connected to the net they went dead on the next bootup, I think the OEMs have something going on there to boot out the older devices so newer ones could be pushed in the market sooner than they were supposed to. Possible.
so, first, in twrp, try to completely format it, follow this to do it
Just, a note: in advanced wipe delete system, data, dalvik cache and cache.
When trying to reboot into system, make sure twrp complains that it have no system. (that way, you know you deleted it)
reboot it, again in twrp.
try to flash custom ROM, should work as it have clean memory.
If it doesnt flash, then make sure to note all log file from twrp while flashing, and post it here, in order to see, what failed in flashing. If it succeds, it should load custom rom . If custom rom dont work, try another one, maybe older, or one that you had previous time (before trying to go into stock rom) (just, to try to boot it somehow. But before trying another custom rom, if one fails, do proper wiping described above.
If that fails try to download oldest stock ROM, and flash it. Maybe newest is blocking it.
If that fails, there is something called EDL mode, when fastboot is not available (for hard brick, like this).
here is video just to give you overview how to do it
and text also
Edit:
WAIT, try to format it, without wiping system. maybe it will boot again.
If not, other solutions are not applicable, if you dont find way to detect that sd card. Only EDL remains.
kraken-gz said:
so, first, in twrp, try to completely format it, follow this to do it
Just, a note: in advanced wipe delete system, data, dalvik cache and cache.
When trying to reboot into system, make sure twrp complains that it have no system. (that way, you know you deleted it)
reboot it, again in twrp.
try to flash custom ROM, should work as it have clean memory.
If it doesnt flash, then make sure to note all log file from twrp while flashing, and post it here, in order to see, what failed in flashing. If it succeds, it should load custom rom . If custom rom dont work, try another one, maybe older, or one that you had previous time (before trying to go into stock rom) (just, to try to boot it somehow. But before trying another custom rom, if one fails, do proper wiping described above.
If that fails try to download oldest stock ROM, and flash it. Maybe newest is blocking it.
If that fails, there is something called EDL mode, when fastboot is not available (for hard brick, like this).
here is video just to give you overview how to do it
and text also
Edit:
WAIT, try to format it, without wiping system. maybe it will boot again.
If not, other solutions are not applicable, if you dont find way to detect that sd card. Only EDL remains.
Click to expand...
Click to collapse
Tried wiping data, cache and dalvik cache and formatting data, none seemed to help
and still no sd card being detected
Now edl mode
I would love to boot into edl mode but the thing is my device isn't being recognised by adb nor is it being recognised by fastboot commands
so that's where I'm stuck for now
OldNoobOne said:
Lol I thought I was the only proper noob here on xda but nice to meet other noobs here too .
I think Kraken-gz is right, once the older devices are OEM off-support its best to stay away from OEM servers, I lost couple of old lesser-known-brand devices to OEM mischief i'd say coz it happened twice to me when I reloaded the original ROMs and tried to connected to the net they went dead on the next bootup, I think the OEMs have something going on there to boot out the older devices so newer ones could be pushed in the market sooner than they were supposed to. Possible.
Click to expand...
Click to collapse
Perhaps that is true