Database Users

Bricked while trying to install Full Android rom.. Now Boot loop into twrp. Pls help.

Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.

puppinoo said:
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
Click to expand...
Click to collapse
Theres a hardware method to boot into the bootloader, this i think you can test, just to see if you can at least get into bootloader.....nothing more
Details in the official nvidia link
http://nv-tegra.nvidia.com/gitweb/?...ob_plain;f=README_SHIELD;hb=rel-22r18-partner
There's a thread here on the "questions" thread with users reporting that the timing of the hardware method can be a pain in the you know where.............might be worth looking into that thread for their experiences in booting the bootloader using the hardware method
Disclaimer:If your brave enough to risk a brick, read on
I suspect this might be the 2.1 stock/twrp issue........current twrp, or current stock dont play nice
Its a good sign that SOMETHINGS loading, rather then NOTHING booting, but dont know if theirs a solution
My analysis of the situation, of what little i know, the -w (wipe) command was expecting a stock recovery but instead got twrp, which is why your in this situation.........maybe, i stress maybe, if you could reflash stock again, you might be able to boot into android stock again and try full android again, leaving out twrp, until a twrp fix is found
Edit
Saying that, if the bootloader is, as i suspect, now using twrp to flash things, then you might be boned....... im no expert on bootloaders, stock "recoveries" and how they work, so i might be wrong on that
Reports around here say that 1.3 stock firmware is the recommended back to stock firmware, apparently, flashing any other firmware versions, bring their own issues.............
From 1.3 stock, use nvidias official OTA to upgrade from 1.3 stock, to 2.1 stock, then try 2.1 full android again...........note, i dont think you can skip firmwares i.e. you have to upgrade to 1.4, then to 2.0, then to 2.1, alot of downloading.......the OTA does'nt give you any other choice
Before doing anything that ive suggested, wait till someone with more experience to come along........i dont want to be responsible for you fully bricking your shield..........just wanna give you an idea of what i think has happened
If worse comes to worse, if you have warrenty, get a replacement
Gd luck........remember, this is an analysis of your predicament of what i THINK might of happened, and what steps, i likely might of entertained.......after looking into it more thouroughly, knowing that i could get a replacement if it went downhill.........so your mileage might vary
Edits
Crappy grammer, further musings, clarifications

Thanks.[/QUOTE]
puppinoo said:
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
Click to expand...
Click to collapse
I had something similar about... shield goes booting in recovery and trying delete some cache and keeps repeat and repeat
Hardware boot in fastboot / bootloader mode
Accessing Bootloader via Hardware
Unplug power from the Shield Android TV. *
Wait a few seconds.
Hold down the power button.
Plug in power
Count to three
Release the power button
You should see the bootloader screen.
If you hold it down too long or not long enough, it simply doesn’t work.
Restore Shield Android TV to Stock
P.s. Personally me I followed this instructions and kind of magically got it in bootloader mode. First done by instruction and then just gave up and pressed randomly and fastboot screen appear. Thanks God I had to done only once, if I would do again I wouldn't had patients
Good luck with this, hope you will get sorted
Here will be link about where I got instructions about hardware boot
http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/
Sent from my Nokia 3310 using free xda app

Thanks a lot fro your help.
I was able to put the box in fastboot mode.
Since I'm not that expert can you tell me where and which rom I have to download (I have a french 16gb version of the box).
Then I'd need to know exactly what commands to performs (even a link to a tutorial is fine).
I really appreciate your help. It seems I can (hopefully) save the box.
EDIT: The fastboot command gave me a (not enough space) when I bricked the box. Is there a risk it could happen again while flashing stock? No idea how much space I have left on the box really.
EDIT2: I found this page: https://developer.nvidia.com/shield-open-source
and I'm downloading this rom called nv-recovery-image-shield-atv-upgrade2_1.zip
and Intend to follow these instructions: http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Can anyone please confirm I'm doing right?

EDIT with joy : I followed all the steps using that rom and it seems everything worked. I reconfiguring the box now. Thanks for help.
basically the procedure I intend to follow is this part (please confirm it's ok):
To flash this recovery image to your SHIELD, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader. Get
DTB file name to use for flashing for your product(see below):
P.s. maybe Since past fastboot commands failed and I only flashed system from zulu99 I could skip the 'fastboot flash boot boot.img' command so if it fails again I still can attempt the fastboot process again?
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb <DTB file name>

puppinoo said:
Thanks a lot fro your help.
I was able to put the box in fastboot mode.
Since I'm not that expert can you tell me where and which rom I have to download (I have a french 16gb version of the box).
Then I'd need to know exactly what commands to performs (even a link to a tutorial is fine).
I really appreciate your help. It seems I can (hopefully) save the box.
EDIT: The fastboot command gave me a (not enough space) when I bricked the box. Is there a risk it could happen again while flashing stock? No idea how much space I have left on the box really.
EDIT2: I found this page: https://developer.nvidia.com/shield-open-source
and I'm downloading this rom called nv-recovery-image-shield-atv-upgrade2_1.zip
and Intend to follow these instructions: http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Can anyone please confirm I'm doing right?
Click to expand...
Click to collapse
You are on the right way with those links
P.s. You can do manual one by one entering or paste and copy those commands or (I'm doing) drag and drop file "flash-all.bat" on cmd previous opened there where you have abd/fastboot etc files and extracted RIGHT FIRMWARE (like shift and right click mouse "open command prompt here"
And after this all sit down and relax
Anyway you are on the right way.
P.s. Hope you download adb fastboot drivers somewhere from Internet !?!
Sent from my Nokia 3310 using free xda app

Startup paralyzes the ASUS logo - ZENFONE 5

Hello!
I have a big problem in my zenfone 5 , I hope someone can help me.
Next , after the last update sent by ASUS My zenfone is simply paralyzed the logo of the manufacturer.
First tried to clear data and cache the recovery without success ... The only option I have left then was to make an update by the ADB . Okay so let's do this, using the ADB 1.0.32 ( I downloaded here on XDA ) I tried to perform the update with several different firmware , but when you get 55% have to return the message " COMMAND NOT FOUND " and the cell appears the logo of broken android
Please help me, how can I fix this. :crying:

amartinss said:
Hello!
I have a big problem in my zenfone 5 , I hope someone can help me.
Next , after the last update sent by ASUS My zenfone is simply paralyzed the logo of the manufacturer.
First tried to clear data and cache the recovery without success ... The only option I have left then was to make an update by the ADB . Okay so let's do this, using the ADB 1.0.32 ( I downloaded here on XDA ) I tried to perform the update with several different firmware , but when you get 55% have to return the message " COMMAND NOT FOUND " and the cell appears the logo of broken android
Please help me, how can I fix this. :crying:
Click to expand...
Click to collapse
Can u upload screen shot of command not found because I m really didn't get u r prblm...one tip go to stock Rom or downgrad to kitkat....

yasin0005 said:
Can u upload screen shot of command not found because I m really didn't get u r prblm...one tip go to stock Rom or downgrad to kitkat....
Click to expand...
Click to collapse
Hi yasin0005
I tried to downgrade to kitkat , but still shows the same message ... I'll post a picture of the device with the messages later ... is that I don't can do it now
See u soon

amartinss said:
Hi yasin0005
I tried to downgrade to kitkat , but still shows the same message ... I'll post a picture of the device with the messages later ... is that I don't can do it now
See u soon
Click to expand...
Click to collapse
Ok...take u r time

yasin0005 said:
Ok...take u r time
Click to expand...
Click to collapse
I can not upload files yet .. I am new to XDA have less than 10 places .. sorry but I can not post the image of the error message. But this is the message that appears on the device ...
Error picture this link amartinss.com.br/sing/IMG_20160101_123536.jpg
OR described below
"Now send the package you want to apply to the device with 'adb sideload <fillenme>'...
Finding update package...
Opening update package...
Verifying update package...
Installing update package...
assert failed: !less_than_int(28686307, getprop("ro.build.date.utc")) || greate_than_int(getprop("ro.build.date.utc"), 1392739200)
return code 8E: Error in /sideload/package.zip
(Status 8)
Installation aborted."
This happens when I try to downgrade the sideload...

To fix your issue, you need to:
1) Update your Recovery to the Latest STOCK version
2) Reinstall your ROM downloading full firmware from ASUS site
The issue is that your ROM/Recovery is not up-to-date to run the update package.

same problem! any solution? can't access fastboot for command "fastboot flash recovery file.img", just adb sideload, but gone wrong in 54%.

patrick.bitencourts said:
same problem! any solution? can't access fastboot for command "fastboot flash recovery file.img", just adb sideload, but gone wrong in 54%.
Click to expand...
Click to collapse
have you found a solution to your problem ???
I am also facing same issue while updating with adb sideload..
if you have got a solution please post it..

Have you tried to acces fastboot with the adb command: adb reboot fastboot ?
Then you could try again to flash your updated recovery.
There is a CWM modified recovery you should try.

keep getting stuck trying to reflash to l29 version.

Ok I'll just rewrite this post instead of starting a new one
Drivers are installed working fine.
Phone is unlocked.
So if I trwp phone at this stage it works and I can root it.
The issue seems to be once I fastboot the 4 files to the phone phone will not boot and hence can not root it.
I've redownloaded the fastbootl29 files still no luck
Am I missing a step is the fastboot stage just sending those 4 files to the phone no unpacking/setup or anything?
Anyone in Aus want to earn some $$$

Got past that stage it's now unlocked and sitting in fastboot mode.
Now when I send the command
Fastboot flash cache c:/1/cache.img
It just says waiting for device any ideas guys

gros31 said:
Got past that stage it's now unlocked and sitting in fastboot mode.
Now when I send the command
Fastboot flash cache c:/1/cache.img
It just says waiting for device any ideas guys
Click to expand...
Click to collapse
Did you tried rebooting ur pc and ur phonte?

Got past that stage. Had to change the boot loader driver.
Load up the l29firmware in 4 parts use twrp then it won't let me root the device like it can't find it.
When trying to boot up the system it just won't boot. Now it's doing its erestore but notice it's looking for the cn firmware.

Huawei P9 lite VNS-L21 Massive Fail. Please help me out

Okay let me explain situation...
I wanted to unlock bootloader,install twrp, root it and install custom rom
I did unlock bootloader with SKRToolHuawei and it was pretty easy,also I installed twrp, then I installed SuperSu in my phone and everything was fine.
Until i dowloaded wrong version of CM 14.1, being a massive noob i though i could change my android 6.0.1 to 7.1 and i got the wrong gaps. In the tutorial it said to wipe cache,dalvid and system. Once i deleted system and got a fail error i realized what I have done and tried cm 13 (Meticulus) and again i got an error message saying that i need twrp version of meticulus.
So I dowloaded that version tried to install with adb using command:
1.Fastboot reboot bootloader
2.Fastboot flash recovery (In the tutorial it said its going to replace old version of twrp so I don't have to delete it)
And I rebooted my Huawei and it does't have a custom recovery for some reason. Now SKRToolHuawei and adb does't see my device and I'm in panic because I don't know what to do: crying::crying::crying:
Nothing works for me and I really need my phone.
Please help poor man out :crying:

Man, you can boot you phone in fastboot mode?
Connected to PC appear as <serial number> when you run command: devices?

gtdaniel said:
Man, you can boot you phone in fastboot mode?
Connected to PC appear as <serial number> when you run command: devices?
Click to expand...
Click to collapse
No, now it does't detect anything after installing meticulus.
I guess it does't have twrp now for some reason
Can you fix it? Please don't say its gone and unfixible

You have to reboot your phone in bootloader...
Until you do that you can not move ahead...

My Redmi Note 7 is stuck in bootloop

Hi everyone,
I've recently rooted my phone and it went pretty much smoothly but i installed an app to change my emojis (i know its dumb but dont judge me ) and i needed to restart my phone so i did it but then my phone was in bootloop.
So I've been on the internet this whole day trying to figure out a way to get my data back and most importantly get my phone back to working.
But i didnt find anything that worked for me, ive tried flashing a fastboot rom but as i was the flash_all.bat program it just crashed so i tried MI Flashing Tool and there i got an error saying "cannot load 'C:\backup': No such file or directory"
Guys i'm desperate its my only phone and I cant afford another right now so any help is grantly appreciated.
Thanks for the help.

U unpack the rom and choice the right direction

You need the boot image of the OS and flash it via fastboot using "fastboot flash boot boot.img" make sure you use the boot image of whichever OS your phone had (stock or custom).
If similarly, the system partition is causing the problem then you need to get the system.img flashed using "fastboot flash system system.img".

We don't even know if his bootloader is unlocked or not.
EDIT: Don't mind me, I don't know how to read.