So I have a noob question for the experts here. I generated my blob and bricksafe image and related tokens. I just can't figure out how to use them to unbrick the tablet. Got the pinwheel of death after updating bootloader and installing cleanrom inheritance. Tried the recommended downgrade method but no luck. TWRP still works like a champ as well as fastboot and APX mode and I can still get into nvflash. Just don't know how to "flash" the images and tokens to get moving again. I looked through thread after thread telling me how to generate but not one to install or use. If there is and I missed it please do point me to it. Any help is appreciated. Thanks in advance.
P.S. Long time lurker but this is my first post. Quite the place you have here.
Chazzfazzle said:
So I have a noob question for the experts here. I generated my blob and bricksafe image and related tokens. I just can't figure out how to use them to unbrick the tablet. Got the pinwheel of death after updating bootloader and installing cleanrom inheritance. Tried the recommended downgrade method but no luck. TWRP still works like a champ as well as fastboot and APX mode and I can still get into nvflash. Just don't know how to "flash" the images and tokens to get moving again. I looked through thread after thread telling me how to generate but not one to install or use. If there is and I missed it please do point me to it. Any help is appreciated. Thanks in advance.
P.S. Long time lurker but this is my first post. Quite the place you have here.
Click to expand...
Click to collapse
Haven't you seen This coming in?
Chazzfazzle said:
So I have a noob question for the experts here. I generated my blob and bricksafe image and related tokens. I just can't figure out how to use them to unbrick the tablet. Got the pinwheel of death after updating bootloader and installing cleanrom inheritance. Tried the recommended downgrade method but no luck. TWRP still works like a champ as well as fastboot and APX mode and I can still get into nvflash. Just don't know how to "flash" the images and tokens to get moving again. I looked through thread after thread telling me how to generate but not one to install or use. If there is and I missed it please do point me to it. Any help is appreciated. Thanks in advance.
P.S. Long time lurker but this is my first post. Quite the place you have here.
Click to expand...
Click to collapse
If your TWRP, fastboot, and adb are still working, then your bootloader and custom recovery are still good.... You may want to format your data partition and wipe everything on your internal SD and then flash your custom ROM again... You may need to check that your TWRP and your bootloader are compatible before installing the custom ROM... Good luck..:fingers-crossed:
graphdarnell said:
Haven't you seen This coming in?
Click to expand...
Click to collapse
I did but I disregarded it since it was done in Linux. I will give it a try though and change commands where needed. Thanks for the reply.
I don't think you need to use the nvflash files as you are not bricked. If you have a spinning wheel and can get to TWRP then make sure you flash the booloader package in the first post of CROMi-X first, reboot and then flash the rom again.
Chazzfazzle said:
I did but I disregarded it since it was done in Linux. I will give it a try though and change commands where needed. Thanks for the reply.
Click to expand...
Click to collapse
You know that you have to boot back into system after flashing the bootloader, do you?
The sequence is:
flash bootloader in TWRP
reboot system
boot back into TWRP
flash rom
Related
Hi, All,
Just now, I followed URL http://forum.xda-developers.com/showthread.php?t=1752270 to succeed bricking my XT897, with boot.img downloaded from CM nightly zip.
Look like my PC can't recognize it now, said no drive. Appreciate all helps on how to un-brick it,
nomos117 said:
Hi, All,
Just now, I followed URL http://forum.xda-developers.com/showthread.php?t=1752270 to succeed bricking my XT897, with boot.img downloaded from CM nightly zip.
Look like my PC can't recognize it now, said no drive. Appreciate all helps on how to un-brick it,
Click to expand...
Click to collapse
Boot to bootloader/fastboot and reflash a known-to-work kernel. On what rom were you on? From which nigttly was the boot.img? It seems like an incompatible or wrong kernel.
You can also flash stock FXZ image or restore nandroid if you made a backup. You should still be able to boot into bootloader and use rsdlite.
nomos117 said:
Hi, All,
Just now, I followed URL http://forum.xda-developers.com/showthread.php?t=1752270 to succeed bricking my XT897, with boot.img downloaded from CM nightly zip.
Look like my PC can't recognize it now, said no drive. Appreciate all helps on how to un-brick it,
Click to expand...
Click to collapse
See mrvek's answer... but honestly why are you following a guide that is not for your device? That is just asking for trouble...
Next time, if the guide is not for your device I would not recommend following it.
Good luck with RSD.
I have an Asus TF300T that I have unlocked, and flashed TWRP 10.6.3.1 onto it. I have then flashed the latest 4.4 Cyanogen nightly, and it bootloops. I think this is because of my bootloader.
Normally once I am at the custom recovery point on a device, I have no further issues and flash rom's like crazy. This specific bootloader requirement is new to me. I've farted around on a few devices before (Moto Milestone, HTC Desire Z, HP Touchpad, Sam GS3), but I'm not very technical.
I think my current bootloader is 10.4.2.18. (It reads Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.4.2.18-20121122" A03).
How do I upgrade my bootloader to allow for 4.4 rom's, and must I downgrade my bootloader if I want to install something like Ubuntu?
The instructions mentioned here http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7 took me to http://forum.xda-developers.com/showthread.php?p=49258989 but neither of these post's seem to be talking about the bootloader. Is there a way to simply upgrade just the bootloader? Or must I flash a special stock Asus rom that upgrades it for me, then reflash TWRP and proceed from there?
I think I may understand. I've downloaded the latest firmware update from the Asus website. Is this zip flashable within TWRP? Or can I simply fastboot the blob within the firmware zip? If so, what would the command be?
jiddahidda said:
I think I may understand. I've downloaded the latest firmware update from the Asus website. Is this zip flashable within TWRP? Or can I simply fastboot the blob within the firmware zip? If so, what would the command be?
Click to expand...
Click to collapse
Use fastboot to install the latest stock blob. Remember to extract the blob file:
Code:
fastboot -i 0x0B05 flash system blob.blob
Then you can flash TWRP 2.6.3.2 and then a KitKat ROM.
I seem to have lost the ability to get it into fastboot mode to apply your instructions. Is it bricked if it bootloops, and I cannot get into that bootloader screen by holding down the volume down button? Your instructions are straight forward but I haven't had a chance to try them yet because of this new issue. So does this sound like it's bricked?
cmendonc2 said:
Code:
fastboot -i 0x0B05 flash system blob.blob
Click to expand...
Click to collapse
Is there another way to get it into fastboot mode? See my post above this one.
I can get into APX mode. Can I fix this using APX mode? I'm googling around but I'll wait for word from you before doing anything, I don't want to make this worse.
jiddahidda said:
I can get into APX mode. Can I fix this using APX mode? I'm googling around but I'll wait for word from you before doing anything, I don't want to make this worse.
Click to expand...
Click to collapse
You cannot use APX mode unless you have already made NvFlash Backups. IF you made then, you can recover using that method.
I seem to have lost the ability to get it into fastboot mode to apply your instructions. Is it bricked if it bootloops, and I cannot get into that bootloader screen by holding down the volume down button? Your instructions are straight forward but I haven't had a chance to try them yet because of this new issue. So does this sound like it's bricked?
Click to expand...
Click to collapse
Yes, that does sound bricked. What you can do is look up Buster's recovery script and try using that to recover. It should be in the General Section.
cmendonc2 said:
You cannot use APX mode unless you have already made NvFlash Backups. IF you made then, you can recover using that method.
Click to expand...
Click to collapse
I think I know the answer, but I'll ask anyway. Is it possible to use someone elses NvFlash backups? I looked into making these backups but never did it .
cmendonc2 said:
Yes, that does sound bricked. What you can do is look up Buster's recovery script and try using that to recover. It should be in the General Section.
Click to expand...
Click to collapse
I've seen you suggest this script several times in several threads, but could never find it. I've been searching for threads with the word Buster or Recovery or Script and I can't find anything that seem's to be what you're talking about? Sorry to be a pain, what's his XDA username?
I think I've found it, but it relies on getting into fastboot, which I can't do. I stumbled on this post earlier while panicing when it first bricked. I think I'm screwed .
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
jiddahidda said:
I think I've found it, but it relies on getting into fastboot, which I can't do. I stumbled on this post earlier while panicing when it first bricked. I think I'm screwed .
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Click to expand...
Click to collapse
Yes, but did you try using the paper clip to reset it? try a few combinations of using it.
I rooted successfully via Towelroot but did not unlock the bootloader. I ran the 1.1 Update and lost root. I ran Towelroot again and rerooted but I had to redownload the binaries and got everything functioning properly. I decided I wanted a custom recovery for backups and such so I installed Flashify and downloaded the CWM recovery file.
Here's the problem. I apparently flashed the recovery as a boot image as I now boot into CWM every time. CWM seems to be functioning properly but the system just boots into CWM every time.
I have not done anything else to try and fix this as I'm feeling rather like, at this point, I'm more likely to break it further if I haven't already broken it beyond repair.
Is there a file I can flash through CWM to restore the correct boot image?
I've been rooting and ROM'ing since early 2010 on my OG Droid and this is the first device I've actually thought I might have flashed myself into a brick but it's also the first device I've tried anything on without an unlocked bootloader.
Any constructive advice will be most appreciated. Thanks.
You are not bricked. Get the recovery image from https://developer.nvidia.com/develop4shield, and enter the bootloader and flash it following the instructions at https://developer.nvidia.com/sites/...eld/SHIELD_tab/HowTo-Flash-Recovery-Image.txt.
In your case you probably only need to flash the boot partition, but if that is not enough then flash them all.
Gnurou said:
You are not bricked. Get the recovery image from https://developer.nvidia.com/develop4shield, and enter the bootloader and flash it following the instructions at https://developer.nvidia.com/sites/...eld/SHIELD_tab/HowTo-Flash-Recovery-Image.txt.
In your case you probably only need to flash the boot partition, but if that is not enough then flash them all.
Click to expand...
Click to collapse
I'm working on it now; thank you! It appears I must be a Registered Developer to d/l the recovery file so I've applied and am awaiting approval.
Narsil007 said:
I'm working on it now; thank you! It appears I must be a Registered Developer to d/l the recovery file so I've applied and am awaiting approval.
Click to expand...
Click to collapse
Here is the boot.img file that you need, extracted from the Nvidia Recovery file.
cam30era said:
Here is the boot.img file that you need, extracted from the Nvidia Recovery file.
Click to expand...
Click to collapse
Fast boot=lifesaver
It took awhile but I'm back in business. Thank you!
Unfortunately, I lost everything and it started with the setup screen but at least I'm not out a $300 tablet :laugh:
Narsil007 said:
It took awhile but I'm back in business. Thank you!
Unfortunately, I lost everything and it started with the setup screen but at least I'm not out a $300 tablet :laugh:
Click to expand...
Click to collapse
Glad to hear it.
Hey guys, posted in a few threads but starting a separate thread to keep my issues out of them.
Anyways, my tablet is out up date and I havent kept up to speed on the last 2 years worth of developments. So im looking to upgrade my rooted and unlocked tablet on 4.1 to the 5.0 rom. My twrp version is 2.3.3.0.
How would i go about updating to a 4.4/5.0 compatible bootloader and recovery?
Ive been advised to update the bootloader, but should i flash the boot before the updated twrp or the other way around? While we're at it, I've noticed the nvflash tools. I'm assuming doing the nvflash stuff would help me recover from any possible bricks?
Any help would be appreciated.
jaydotelloh said:
Hey guys, posted in a few threads but starting a separate thread to keep my issues out of them.
Anyways, my tablet is out up date and I havent kept up to speed on the last 2 years worth of developments. So im looking to upgrade my rooted and unlocked tablet on 4.1 to the 5.0 rom. My twrp version is 2.3.3.0.
How would i go about updating to a 4.4/5.0 compatible bootloader and recovery?
Ive been advised to update the bootloader, but should i flash the boot before the updated twrp or the other way around? While we're at it, I've noticed the nvflash tools. I'm assuming doing the nvflash stuff would help me recover from any possible bricks?
Any help would be appreciated.
Click to expand...
Click to collapse
Yes here you are ....
Get the SKU from your bootloader screen .....
Then go to the Asus website and get the firmware for your SKU ending in 27.5 ...
Then unpack the zip and there will be another zip unzip it you will find a file called blob ....
Flash this blob from fastboot ...
Let me know if you need any help along the way..
Thx Josh
lj50036 said:
Yes here you are ....
Get the SKU from your bootloader screen .....
Then go to the Asus website and get the firmware for your SKU ending in 27.5 ...
Then unpack the zip and there will be another zip unzip it you will find a file called blob ....
Flash this blob from fastboot ...
Let me know if you need any help along the way..
Thx Josh
Click to expand...
Click to collapse
Thanks for following me around my 3 posts, lol.
Quick questions:
1. Should I flash the bootloader BEFORE flashing the updated TWRP? Or does the new TWRP get flashed before the bootloader.
2. When I flash the new bootloader, will i still be able to run 4.1 on the tablet (i.e. is the new bootloader backwords compatible?)
3. Will the NVFLASH stuff help me in the event that I do mess something up? Seems like it supposed to be a brick-proof safety net in case something goes wrong.
thanks for the help man!
jaydotelloh said:
Thanks for following me around my 3 posts, lol.
Quick questions:
1. Should I flash the bootloader BEFORE flashing the updated TWRP? Or does the new TWRP get flashed before the bootloader.
2. When I flash the new bootloader, will i still be able to run 4.1 on the tablet (i.e. is the new bootloader backwords compatible?)
3. Will the NVFLASH stuff help me in the event that I do mess something up? Seems like it supposed to be a brick-proof safety net in case something goes wrong.
thanks for the help man!
Click to expand...
Click to collapse
1. The blob file contains the SOS which is the stock recovery, so flash TWRP after ....
2. No you would have to revert back to a 4.1 bootloader to do that ...
3. Yes I would highly recommend doing this ......
4. If you need any help ever shoot me an email we can hangouts [email protected]
Thx Josh
lj50036 said:
1. The blob file contains the SOS which is the stock recovery, so flash TWRP after ....
2. No you would have to revert back to a 4.1 bootloader to do that ...
3. Yes I would highly recommend doing this ......
4. If you need any help ever shoot me an email we can hangouts [email protected]
Thx Josh
Click to expand...
Click to collapse
Thanks Josh, I think I know what to do now:
Step 1: Set up NVFLASH and get my backup files.
Step 2: Flash the 27.5 Bootloader using fastboot.
Step 3: Flash TWRP openrecovery-twrp-2.8.1.0-tf300t.blob
Step 4: Wipe system/cache, etc
Step 5: Flash Katkiss 5.0
Is this correct? Am i missing any steps in there?
Looks like you're not on hangouts right now, shoot me a message if we can chat. [email protected]
So, Josh TOTALLY hooked me up on this issue. Not only offer his help, he actually walked me through the entire process watching my screen through screenshare. I'm now up and running on Kitkass 5.0.... sweet sweet lollipop goodness.
Not sure how to edit the title to solved, but maybe a mod could do that?
jaydotelloh said:
So, Josh TOTALLY hooked me up on this issue. Not only offer his help, he actually walked me through the entire process watching my screen through screenshare. I'm now up and running on Kitkass 5.0.... sweet sweet lollipop goodness.
Not sure how to edit the title to solved, but maybe a mod could do that?
Click to expand...
Click to collapse
If you go to edit your first post and then go to adv edit, there you can add 'SOLVED'
Thx Josh
Hi Everyone!
Because of having issues i can´t fix on my OnePlus, i´m finally asking for some professional help here, as it´s getting more and more complicated and i don´t want to ruin my phone.
What was my plan?
Installing CM11S 44S on my OPO, which had the 05Q Version as factory setting.
Also i wanted to install a franco kernel.
I hoped, if i do both steps successfully, my OPO will have a good battery life (44S seemed to be the most efficient version, according to some forums).
What did i do so far?
First i set up an adb backup for my data, but not for the OS. However, i installed SDK plus tools and drivers.
Next step was installing a new recovery, which is able to flash a new version of CM11S, so i set up TWRP with fastboot, which means my device is "unlocked" now.
Everything worked well so far, i also made an backup in TWRP.
The problem:
I wanted to reboot my OPO at some point and TWRP asked me for rooting my device. Accidentally i swiped over so it started rooting process, but i didn´t want to root it, so i immediately shut the device down.
By now TWRP recovery/fastboot is working, but my OS 05Q is lost and i can´t install a new ROM because im getting the Report:
--
Checking for MD5 file...
Skipping MD5 check; no MD5 file found
Error flashing zip /<path to .zip file>
--
Can anyone help me to get 05Q back or the 44S with the franco kernel?
I know there might be some other threads that deal with similar problems, but actually none of them helped me so far. For example: do i need a fastboot image or signed flashable zips (which i have)? In which order do i install the kernel and the ROM?
Some Information:
I can access my device via fastboot and my OPO is also shown as a adb device on my MAC.
When starting in TWRP, i can also access the device in USB Mode, transfering files is also possible.
I´m not really competent with android modding or programming, so i will need some noob-friendly answers, but i bet you guys know how to help me out here.
Thank you very much for your help, i really don´t know what to do anymore.
EDIT:
I found out how to place a md5 file to the referring version, but it still sais: MD5 does not match.
I´m so done with it right now that i wish i had my OPO back as it was few days ago.
Well, i cant really help here as i have not face this problem but ur mistake was that u Immediately shut the device down the moment it was installing root. It may have corrupted the partitions of the phone and left it at that state, so maybe restoring the partitions of that section may help. Like i said im not knowledgeable about this
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Heisenberg said:
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Click to expand...
Click to collapse
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Thyrix said:
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Click to expand...
Click to collapse
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Heisenberg said:
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Click to expand...
Click to collapse
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Thyrix said:
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Click to expand...
Click to collapse
You need the fastboot images.
Heisenberg said:
You need the fastboot images.
Click to expand...
Click to collapse
Got stuck at step 2: It Terminal said error: cannot determine image filename for sbl1.mbn - although the name is correct and the file is in the correct folder :/
EDIT:
Fixed it, forgot to type sbl1 2 times, im sorry
And it worked, thank you sooooo much!!!