I think I finally bricked my device. I'm guilty. Just want to keep track of everything I did and share how it's bricked.
1. Everything starts because the 4g LTE stopped working. The device starts to give me "Invalid SIM" message no matter how I try. Same message with either T-mobile sim card or the stock AT&T sim card. At this time, the device is on TWRP 2.8.1.0 with Thor Gapps Rom ( 13.3.2.4 ).
2. Thinking it might be a ROM issue, I restored 13.3.2.3.2. Same error message: Invalid SIM.
3. Thinking to restore everything stock before returning it to amazon, I flash stock recovery.img to overwrite TWRP and restored 13.3.2.6 backed-up with safestrap. System starts up but has some issue: it always goes back to selecting language page.
4. Flashed update-kindle-13.4.5.2_user_452004120-twrp.zip to stock slot with safestrap in hope of fixing everything. Now system stalls at the white "Kindle fire" screen.
I know that zip is for twrp, but I thought twrp can take backup made with safestrap, why not the other way around?! Well, I'm unlucky this time. One shall never touch stock slot with safestrap. I think I should have used the official update-kindle-13.4.5.2_user_452004220.bin and update through Device-update menu. Oh well.
Any way I can still play with this device before it set off for amazon?
In
shadowcliffs said:
I think I finally bricked my device. I'm guilty. Just want to keep track of everything I did and share how it's bricked.
1. Everything starts because the 4g LTE stopped working. The device starts to give me "Invalid SIM" message no matter how I try. Same message with either T-mobile sim card or the stock AT&T sim card. At this time, the device is on TWRP 2.8.1.0 with Thor Gapps Rom ( 13.3.2.4 ).
2. Thinking it might be a ROM issue, I restored 13.3.2.3.2. Same error message: Invalid SIM.
3. Thinking to restore everything stock before returning it to amazon, I flash stock recovery.img to overwrite TWRP and restored 13.3.2.6 backed-up with safestrap. System starts up but has some issue: it always goes back to selecting language page.
4. Flashed update-kindle-13.4.5.2_user_452004120-twrp.zip to stock slot with safestrap in hope of fixing everything. Now system stalls at the white "Kindle fire" screen.
I know that zip is for twrp, but I thought twrp can take backup made with safestrap, why not the other way around?! Well, I'm unlucky this time. One shall never touch stock slot with safestrap. I think I should have used the official update-kindle-13.4.5.2_user_452004220.bin and update through Device-update menu. Oh well.
Any way I can still play with this device before it set off for amazon?
Click to expand...
Click to collapse
Did you already try just holding onto the power button for over 20sec , to force a hard reset and get back into RECOVERY
the rest I'm not sure about you say you are on Thor gapps? with our new 2. 8. 1. 0?
did he make that compatible? I didn't realize Thor gapps was compatible
and what are you even doing with the update .5.2 ?that is the KitKat update and is completely incompatible with safestrap or older kernels so I am really confused on what you have stated in above post
or do you have that TRW P recovery flashed and somehow using safestrap also?
looks like to me you have flashed everything but the right thing but then again it's really hard to tell what you have going on here.
Holding the power button for over 20 sec does me nothing. I can enter "Kindle Fire System Recovery" the same way I entry twrp though by holding power and volume up during booting. There are two options there:
Reboot your Kindle
Reset to Facotry Defaults
I tried both and none helped me to boot into system.
I hate it that HDX is not like Samsung Galaxy phones which have a true recovery mode that can flash file, or a download mode that allows access via adb.
I think the reason that my hdx is bricked are:
1. First, I overwrote twrp with stock recovery 13.3.4 (because I want to restore to stock mode for return). Otherwise if I can still enter twrp, I will be saved.
2. Second, the file I flashed to stock slot with safestrap, update-kindle-13.4.5.2_user_452004120-twrp.zip, is made to boot with twrp. I guess it doesn't go well with the stock recovery 13.3.4.
jimyv said:
InDid you already try just holding onto the power button for over 20sec , to force a hard reset and get back into RECOVERY
the rest I'm not sure about you say you are on Thor gapps? with our new 2. 8. 1. 0?
did he make that compatible? I didn't realize Thor gapps was compatible
and what are you even doing with the update .5.2 ?that is the KitKat update and is completely incompatible with safestrap or older kernels so I am really confused on what you have stated in above post
or do you have that TRW P recovery flashed and somehow using safestrap also?
looks like to me you have flashed everything but the right thing but then again it's really hard to tell what you have going on here.
Click to expand...
Click to collapse
Related
hi all
just wanted to star a discussion about this topic..
anybody know, how's the progress in getting a CWM for MediaPad?
thanks a lot
Backup works, but restoring a backup doesn't restore every setting. So i would say it's a WIP. But maybe segler11 or brainmaster can tell more about it.
Eagerly awaiting for this to be done.
Androod-hilfe.de has a clockwork RECOVERY.
Gesendet von meinem HUAWEI MediaPad mit Tapatalk
Is there a way to get a hold of this?
Sent from my HUAWEI MediaPad using XDA
I would love to break my tablet in the name of getting it to work
Sent from my HUAWEI MediaPad using XDA
@cosmique
Like I said, it's a WIP and restoring a Backup doesn't work 100% afaik... But if someone wants to try it here, go ahead. I'll upload it.
€dit: Done
Original Thread: here.
WARNING: I'm not responsible for any damage on your devices. This has only been tested on a european Huawei Mediapad and is based on the 2nd Preview of ICS
Code:
fastboot flash recovery recoveryxxxx.img
fastboot flash recovery2 recoveryxxxx.img
Important: If you want to restore a backup use
Code:
wipe data/factory reset
wipe cache partition
first !
After a "wipe data/factory reset" and "wipe cache partition" the first boot could take at least 10 minutes.
If you want to flash AddOns like GApps.zip no wipe is needed
After restoring a Backup, ALL apps are restored but not all app-settings.
Remember: It's a BETA-Release !
Click to expand...
Click to collapse
All credits go to DS7005, segler11 and brainmaster
Just a helpful hint: Titanium Backup can now restore app data directly from nandroid backups. So if the biggest issue right now is failure to restore app data, in a pinch Titanium can fill in the blanks.
Sent from my Galaxy Nexus using Tapatalk
Recovery flashed successfully but when I perform a backup, it says that the backup path can't be mounted. This is on a Springboard running ICS Beta 2.
Bump. Any further progress?
So it has been quite some time since I have heard anything about CWM for our device. Does anybody have an update? What the heck ever happened with the folks working on it over in Germany?
rkwhyte2 said:
So it has been quite some time since I have heard anything about CWM for our device. Does anybody have an update? What the heck ever happened with the folks working on it over in Germany?
Click to expand...
Click to collapse
Last time I tried the download at post #7 it worked for the basic. As described by Rumbi it may not restore widgets and some setting.
The downside is that you have to reinstall original "boot.img" and "recovery.img" to be able to update to next version, every time
I think that as things get stabilized on the ICS firmware there will be more work for it !
Question: Is there any recovery.img available that would be equivalent to stock recovery on a Springboard?
In other words... if I upgrade a Springboard to MediaPad ICS... then later revert to 3.2 from a nandroid backup, is there a recovery.img that I can flash so that OTA updates will work again?
Okay I flashed the CWM img successfully in fastboot on my Springboard...
But what I'm confused about is, how do I boot into recovery now? I have tried every combination and I always get either fastboot or regular boot.
Do I have to already have ICS for this recovery to work?
Update: Ok I managed to figure out the trick is to hold the volume down button, press power for 2 seconds until it vibrates, let go of power and continue holding the volume until recovery starts.
The problem is I always get stock recovery, which gives me a FAIL message.
I discovered that on my Springboard I have the May 2012 OTA update already installed, which included the dreaded /system/recovery-from-boot and /etc/install-recovery files. This means any time it boots successfully into the OS, it reinstalls the stock recovery.
So now I have a paradox because I'm still not rooted yet. I can install CWM from fastboot, but there is no way to cleanly power down the tablet. I have been unable to force it from fastboot directly to recovery, because the only way to get it out of there is to hold down the power button which... yup, starts rebooting into the OS. I can hold down power during that reboot cycle, but again it just initiates a reboot and not a power down.
So how do I get into recovery after flashing CWM in fastboot... without letting it boot the OS before I get there?
So far the only idea I have remaining is to flash CWM in fastboot and then just leave it on the fastboot screen, stick it in a box somewhere, and come back in a day or so when the battery has died. Charge it up and then boot it into recovery. A little extreme?
Boot into fastboot normally pressing power and VOL-
When in fastboot press the power button for 10 sec to reboot and then keep pressing the VOL+ button, it'll show the mediapad logo twice and the you will be in the cwm.
Hope it helps.
dark_fighter said:
Boot into fastboot normally pressing power and VOL-
When in fastboot press the power button for 10 sec to reboot and then keep pressing the VOL+ button, it'll show the mediapad logo twice and the you will be in the cwm.
Hope it helps.
Click to expand...
Click to collapse
I tried that. It just booted into the OS.
Also the Springboard firmware has an annoying loud T-Mobile startup chime, so to be considerate with my roommate, the moment I see it booting into the OS I have to wrap it with my duvet in order to muffle the sound
Is it possible this CWM just isn't compatible with the Springboard on Honeycomb?
Just a question... if you want to update to ICS but stock, why don't you use the official rom from Huawei? and If you don't like it you can always flash back a HC rom from Huawei.
Sorry if I didn't get something and this is a stupid suggestion
Huawei doesn't offer any stock ROM files for the Springboard. I would like to install and run CWM from the Springboard while leaving the T-Mobile Honeycomb intact, in order to root it without any other modifications.
Sent from my Galaxy Nexus using Tapatalk 2
UPDATE: I did not notice at first that I had to flash both recovery *and* recovery2.
Even after noticing this, I was unable to leap from fastboot straight into recovery. However, I left it in fastboot this morning after flashing, to drain the battery. Then I got home and plugged it in to charge for about 5 minutes. I unplugged it, used the recovery key combo, and FINALLY made it into CWM! I used an SD adapter to copy su.zip onto the microSD, plugged in, remounted /sdcard and installed that zip. I have plugged it back in to charge, and I am doing a nandroid backup of stock rooted.
First thing I will have to do once booted is install Root Explorer and rename the offending files that keep replacing CWM. Then I'll be off to the races.
EDIT: The backup stalled during the system partition. Don't know why. Maybe something different about the layout of Springboard vs. MediaPad.
Also, adb in recovery does not work (unless there is a driver I am missing? but ADB works for me booted into the OS). That's unfortunate - this is an incredibly useful feature of CWM that should get fixed up ASAP.
I also noticed that a 10 second press of the power button actually shuts it down from CWM, as opposed to the reboot I get from fastboot or anywhere else in the OS.
EDIT again: Oh crap crap crap. Now it just bootloops when I try to start it up! This does not bode well. All I did was install a superuser zip, and attempt a nandroid backup.
FINAL edit once more again: Okay well now I'm back to square minus one. I wiped userdata and it still bootlooped. So then I tried flashing the system img from this thread:
http://forum.xda-developers.com/showthread.php?t=1550694
No more bootloop. It's booted up. The firmware is now an older one than what I received it with. Oddly when I did "fastboot erase userdata" from fastboot it did NOT actually wipe anything! It still remembers my desktop, wifi passwords, installed apps etc.
On the bright side - the dreaded recovery-reinstalling files are not in this system.img.
Hi, my G3 (vs985) was running 24b, rooted, and I installed TWRP Manager and installed a custom recovery. all went fine until I got a secure boot error whenever I booted to recovery. After tinkering and thinking I found a possible solution, I used autorec which gave a Success in installing twrp, and booted back in to recovery where I got a into an LG Security Error and would continue switching between the logo and the security error screen. I was still able to get into twrp through the factory recovery menu and going to factory reset which sends me to twrp. I tried restoring a backup I had previously made, and that went successfully but now my issue is that I'm stuck in a boot certification error with the light blinking blue and red and I am unable to get into download mode, but am still able to get into twrp and get into my phone's files. I don't trust myself anymore, and would absolutely love some guidance on this. If I do try to go to download mode, and I connect it to my pc, my pc makes the noise as if it were connecting, and the phone vibrates, but the screen turns black and nothing "seems" to pop up. I can try to answer any questions, I am somewhat new to this. Thank you in advance!
EDIT: The error I'm currently getting is:
"Secure Boot Error
Cause: Boot Certification Verify".
I'm guessing that you used the 23C autorec which put the wrong bootloader on the phone for 24B. From TWRP. I'd create a backup in TWRP, dirty flash JasmineROM 8.0 (in other words, no wiping), then you should be good.
I had this yesterday. Did the same thing.
I finally resolved it by getting back into TWRP from the OEM recovery, Full System Wipe menu item. TWRP allowed me to mount the storage on my computer and flash SkyDragon 5.0. I still can't get back into recovery, but at least the phone works better than stock Lollipop.
BoulderGeek said:
I had this yesterday. Did the same thing.
I finally resolved it by getting back into TWRP from the OEM recovery, Full System Wipe menu item. TWRP allowed me to mount the storage on my computer and flash SkyDragon 5.0. I still can't get back into recovery, but at least the phone works better than stock Lollipop.
Click to expand...
Click to collapse
Boulder, I'm not sure I understand what you wrote, twrp is recovery, so if you can flash using twrp are you just unable to access it ...it must me installed on your phone? I haven't flashed using the computer in a long time, so it's not really fresh in my mind what you did. If you power down your phone, then hold the power and vol down button simultaneously, it will reboot, release buttons, then as soon as you see the lg logo, press the power/volu down simult. again, and it will take you to a screen that gives you options you can choose using the volume up/down keys to navigate and power to choose a button. Wipe cache would take you into twrp if it is indeed installed on your phone. If you can access twrp however you did previously,you can flash a zip file of twrp (I use 2.8.7.0, I think it is the newest, it is newer than what was in autorec that I tried last night). Wipe davalcik/cache after you flash the twrp zip and reboot your phone and you should be fine....although I think you may actually have twrp already (hence 'recovery"} based on what you posted. Good luck.
I did flash the 23C version of Autorec into my 24b phone. This gave me the Security Error bootloop.
Eventually I was able to get into LG stock recovery with the volume down button. Magically, hitting Factory Wipe brings me to the hidden TWRP. From there I flashed base SD5.0. In Android, I installed the Autorec 24b apk and reinstalled TWRP. This again security looped.
Now, I can't even access LG bootloader or TWRP. Even the QuickBoot app fails to boot to revovery. But, the phone works, so I don't want to break it further. Might just wait for a development upgrade to SkyDragon.
I mistakenly flashed it to force Google Play store onto it as it was failing to work through other methods. Now all I get when it boots up is the welcome Google screen you get when you turn on an Android tablet for the first time. I can enter the Kindle settings and use wifi but I can't get to the launcher screen. I have tried to put the Fire into Amazon recovery mode using the volume down and power but it just turns on and off. Safestrap appears as disabled on the stock slot and can't see the stock rom I have put into the internal storage. Even though it isn't bricked there seems to be no way to flash a rom back and regain full control. I think the Gapps flash corrupted the firmware. In the settings I still see my firmware 4.5.2. I tried factory restoring it, wiping everything using Safestrap, but nothing works.
loughrey101 said:
I mistakenly flashed it to force Google Play store onto it as it was failing to work through other methods. Now all I get when it boots up is the welcome Google screen you get when you turn on an Android tablet for the first time. I can enter the Kindle settings and use wifi but I can't get to the launcher screen. I have tried to put the Fire into Amazon recovery mode using the volume down and power but it just turns on and off. Safestrap appears as disabled on the stock slot and can't see the stock rom I have put into the internal storage. Even though it isn't bricked there seems to be no way to flash a rom back and regain full control. I think the Gapps flash corrupted the firmware. In the settings I still see my firmware 4.5.2. I tried factory restoring it, wiping everything using Safestrap, but nothing works.
Click to expand...
Click to collapse
Responded here (double post).
You were fortunate attempts to access the native Amazon recovery menu failed as resetting from there will immediately brick the device with no possibility of recovery when Safestrap is installed. See link above for other suggestions. You need to do most of the repair work from within Safestrap recovery.
Further thoughts:
- flashing GApps over FireOS 4.5.2 is untested and likely led to your current situation (where did you read that was an option?)
- do not reset or wipe anything unless advised to do so by an experienced contributor as it will only make the situation worse and likely eliminate any hope of recovery
- if you never attempted to flash a custom rom (Nexus or CM11) then there is no image file to work from in Safestrap greatly limiting recovery options
- with WiFi functional and access to Kindle Settings you may be able to enable USB debugging (please try)
- if sucessful you may be able to transfer a rom image to your device via tether and then flash with Safestrap; please ask which files are suitable if you get that far
Download Safestrap-compatible stock image
Copy file onto tablet
Boot into Safestrap, flash the aforementioned file
Remember to disable OTA updates
EncryptedCurse said:
Download Safestrap-compatible stock image
Copy file onto tablet
Boot into Safestrap, flash the aforementioned file
Remember to disable OTA updates
Click to expand...
Click to collapse
Yes - this would be the most expeditious route of you can gain sufficient control when booting FireOS to 'see' the device when tethered. Ideally it will show up in Windows and you can simply copy the file to 'internal storage'. Failing that you will need to enable USB debug (as mentioned in an earlier post) and then use adb to push the file onto your device.
If you are successful in getting an image file on your device don't delete it even if things work out ok! With Safestrap you should always keep an flashable rom on your device for recovery purposes. The FireOS rom weighs in around 800 MB. If space is a concern the Nexus v4 and CM11 roms are somewhat smaller, <300 MB. Even if you never plan to run these roms they can be used for emergency recovery.
Hey guys,
Got a no name phone with mtk6580 and kernel 3.10.72 running custom Chinese android 5.1, and as you probably guessed I got problem flashing custom recovery on it, the device is not on the list for neither TWRP nor CWP.
What to do?
Thank you
Vant2239 said:
Hey guys,
Got a no name phone with mtk6580 and kernel 3.10.72 running custom Chinese android 5.1, and as you probably guessed I got problem flashing custom recovery on it, the device is not on the list for neither TWRP nor CWP.
What to do?
Thank you
Click to expand...
Click to collapse
A good place for no name phones is here:
https://forum.hovatek.com/forum-76.html
Either have a search or put a request for someone to make a TWRP for your phone, I put a request in and the next day someone made one for me.
I did try to make my own from a guide on here, its apparently really easy but I just couldnt get it to work, here is the one someone made for me which may work or at least gives you a good starting base to try: http://www.needrom.com/download/uhappy-up580-twrp-recovery/
robneymcplum said:
A good place for no name phones is here:
https://forum.hovatek.com/forum-76.html
Either have a search or put a request for someone to make a TWRP for your phone, I put a request in and the next day someone made one for me.
I did try to make my own from a guide on here, its apparently really easy but I just couldnt get it to work, here is the one someone made for me which may work or at least gives you a good starting base to try: http://www.needrom.com/download/uhappy-up580-twrp-recovery/
Click to expand...
Click to collapse
Once again thanks a lot for reply!
I have successfully ported one of your builds, but with some mindless actions trying to flash recovery through fast boot got a boot loop of some sort, logo keeps appearing and phone doesn't boot.
What I did is in fastboot flashed recovery with help of 'fastboot oem unlock' and now I just stuck. I have stock recovery, tried to flash it back but unsuccessfuly. Any idea how can I fix it?
Sorry for being such a noob
recovery and/or firmware should be flashed with SPflash tool simply because I find its the easiest way,
Perfect way of doing things is:
SPflash tools=flash stock firmware til 'done' close SPflash
remove battery, put back in, boot, maybe stuck on boot image (happens to me 50% of the time)
remove battery, put back in, boot. Let it boot up and set up wifi/internet
turn off phone, battery out, back in DONT POWER ON
reopen SPflash, select correct scatter.txt file from stock firmware again
unselect all tick boxes, tick recovery box, click on 'address or location of recovery' and locate the TWRP image
click download, plug turned off phone in.
wait til done.
battery out, back in, boot to recovery with correct button presses (volume up+power?)
in recovery, set correct time
reboot recovery and allow install of superSU, reboot phone, select superSU from the notification and update.
Then put the new custom rom onto sdcard and reboot back to recovery, wipe system/data/cache/dalvik cache and install rom
install gapps
wipe caches
reboot
That is a perfect way of doing it, if the rom doesnt boot something is wrong with the rom/boot img/something
fix that, put back onto sdcard, just do the 4 wipes again and install rom again
and again
and again
until it is fixed and boots.
robneymcplum said:
recovery and/or firmware should be flashed with SPflash tool simply because I find its the easiest way,
Perfect way of doing things is:
SPflash tools=flash stock firmware til 'done' close SPflash
remove battery, put back in, boot, maybe stuck on boot image (happens to me 50% of the time)
remove battery, put back in, boot. Let it boot up and set up wifi/internet
turn off phone, battery out, back in DONT POWER ON
reopen SPflash, select correct scatter.txt file from stock firmware again
unselect all tick boxes, tick recovery box, click on 'address or location of recovery' and locate the TWRP image
click download, plug turned off phone in.
wait til done.
battery out, back in, boot to recovery with correct button presses (volume up+power?)
in recovery, set correct time
reboot recovery and allow install of superSU, reboot phone, select superSU from the notification and update.
Then put the new custom rom onto sdcard and reboot back to recovery, wipe system/data/cache/dalvik cache and install rom
install gapps
wipe caches
reboot
That is a perfect way of doing it, if the rom doesnt boot something is wrong with the rom/boot img/something
fix that, put back onto sdcard, just do the 4 wipes again and install rom again
and again
and again
until it is fixed and boots.
Click to expand...
Click to collapse
Im getting an error when try to flash it: ERROR: S_DL_GET_DRAM_SETTING_FAIL (5054)
trying to flash stock firmware?
I had numerous issues getting mine to flash the first time, I downloaded and tried different versions of SPflash tools, different USB leads/ports etc...
I have to use a USB lead from my moto x play as the stock lead wouldnt work, my galaxy tab lead wouldnt work either.
I have to use SPflash tool version SP_Flash_Tool_exe_Windows_v5.1552.00.000 as other versions kept bringing up that error and similar ones.
It really does seem to be trial and error unfortunately.
Hey, new here....
So a while back a rooted my phone, which I followed a tutorial and all was fine, my phone has been fine. But today I decided I didn't want it rooted anymore and just wanted a clean install asif the phone was brand new, so I went into backup in settings and pressed complete system reboot and confirmed...
Then after a few minutes it send med to my team win recovery project recovery (the custom recovery I had flashed in order to root)
And so on there I reinstalled backup...
But now basically im stuck in a total loop where it will not let me do anything except load up twrp! =(
Even when I switch off and back on just straight to twrp... I have done "wipe" option, done "restore" option to no avail.
I want to get rid of twrp and just clean install nougat, is there anway I can do or have I ruined my phone?
Many thanks anyone who can help...
louiewm said:
Hey, new here....
So a while back a rooted my phone, which I followed a tutorial and all was fine, my phone has been fine. But today I decided I didn't want it rooted anymore and just wanted a clean install asif the phone was brand new, so I went into backup in settings and pressed complete system reboot and confirmed...
Then after a few minutes it send med to my team win recovery project recovery (the custom recovery I had flashed in order to root)
And so on there I reinstalled backup...
But now basically im stuck in a total loop where it will not let me do anything except load up twrp! =(
Even when I switch off and back on just straight to twrp... I have done "wipe" option, done "restore" option to no avail.
I want to get rid of twrp and just clean install nougat, is there anway I can do or have I ruined my phone?
Many thanks anyone who can help...
Click to expand...
Click to collapse
Flash stock nougat rom using spflash tools. that should fix it. if that doesnt work install marshmallow
louiewm said:
Hey, new here....
So a while back a rooted my phone, which I followed a tutorial and all was fine, my phone has been fine. But today I decided I didn't want it rooted anymore and just wanted a clean install asif the phone was brand new, so I went into backup in settings and pressed complete system reboot and confirmed...
Then after a few minutes it send med to my team win recovery project recovery (the custom recovery I had flashed in order to root)
And so on there I reinstalled backup...
But now basically im stuck in a total loop where it will not let me do anything except load up twrp! =(
Even when I switch off and back on just straight to twrp... I have done "wipe" option, done "restore" option to no avail.
I want to get rid of twrp and just clean install nougat, is there anway I can do or have I ruined my phone?
Many thanks anyone who can help...
Click to expand...
Click to collapse
All you got to do is download sp_flash tool latest version, load the scatter file of rom, then simply go to options and then click to Connection, set usb speed to full speed, and Battery to w/o battery. Then make sure you have selected all the files needed to flash, next click the start button and connect your elephone while holding the volume + button. It will take a quite while but it will be successful.