[Q] Boot loop on green robot - Asus Eee Pad Transformer Prime
Hello,
My tablet is bootlooping on green robot.
unable to go to RCK
vol- and power don't work... have to use "adb reboot-bootloader" during green robot to have menu RCK/usb/fastboot/wipe
history
I've wanted to uppgrade my tf201 from CM11 unofficial to f2fs version (cm-11-20141104-UNOFFICIAL-tf201).
installed twrp 2.8 f2fs
installed F2FS-Geass_Public_7
installed CUSTOM_TWRP_JB_KK_v2.8_DEV_TF300T-signed
never worked, always have preinit failed rc=-1 errno=8
i've try to go backward with cmw... bricked!
Have somes pics but can't post cause i'm too young here!
orcad.fr said:
Hello,
My tablet is bootlooping on green robot.
unable to go to RCK
vol- and power don't work... have to use "adb reboot-bootloader" during green robot to have menu RCK/usb/fastboot/wipe
history
I've wanted to uppgrade my tf201 from CM11 unofficial to f2fs version (cm-11-20141104-UNOFFICIAL-tf201).
installed twrp 2.8 f2fs
installed F2FS-Geass_Public_7
installed CUSTOM_TWRP_JB_KK_v2.8_DEV_TF300T-signed
never worked, always have preinit failed rc=-1 errno=8
i've try to go backward with cmw... bricked!
Have somes pics but can't post cause i'm too young here!
Click to expand...
Click to collapse
No wonder! If you see 4 icons, you are on ICS bootloader, you shouldn't have flashed @ne0zone75's TWRP.
So, where are you standing now? Are you able to fastboot?
das chaos said:
No wonder! If you see 4 icons, you are on ICS bootloader, you shouldn't have flashed @ne0zone75's TWRP.
So, where are you standing now? Are you able to fastboot?
Click to expand...
Click to collapse
Thanks for your answer,
When i try to flash @ne0zone75's TWRP., i have foollowing errors :
C:\adb>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
emulator-5554 offline
015d07877730060e device
C:\adb>adb -s 015d07877730060e reboot bootlader
C:\adb>fastboot -i 0x0b05 flash recovery ne0zone75_tf300t.blob
sending 'recovery' (7354 KB)...
OKAY [ 1.690s]
writing 'recovery'...
OKAY [ 0.920s]
finished. total time: 2.610s
C:\adb>fastboot -i 0x0b05 reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.000s
C:\adb>
Click to expand...
Click to collapse
it doesn't reboot at last step....
I i don't have access to boot menu anymore... (vol- or adb)
orcad.fr said:
Thanks for your answer,
When i try to flash @ne0zone75's TWRP., i have foollowing errors :
it doesn't reboot at last step....
I i don't have access to boot menu anymore... (vol- or adb)
Click to expand...
Click to collapse
You should not flash @ne0zone75's TWRP with the wrong bootloader!
So you can't fastboot anymore? And you certainly don't have your nvflash files? Then you are bricked!
das chaos said:
You should not flash @ne0zone75's TWRP with the wrong bootloader!
So you can't fastboot anymore? And you certainly don't have your nvflash files? Then you are bricked!
Click to expand...
Click to collapse
When i have unlocked my tf201 and put on it CM11 unofficial, i've extracted this files before :
androidroot
24/04/2014 12:10 1*670*651 blob.bin
24/04/2014 12:10 649 blob.log
24/04/2014 12:10 1*558*608 bootloader.ebt
24/04/2014 12:10 6*128 create.bct
24/04/2014 12:05 298 pt_patch.log
24/04/2014 12:10 299 pt_restore.log
24/04/2014 12:10 6*128 recovery.bct
7 fichier(s) 3*242*761 octets
Click to expand...
Click to collapse
Does i have a chance?
orcad.fr said:
When i have unlocked my tf201 and put on it CM11 unofficial, i've extracted this files before :
Does i have a chance?
Click to expand...
Click to collapse
Any chance in the world! You are unbrickable (almost).
Follow this:
First you have to reset bootloader using wheelie routine:
1. Put tab in apx mode (power + vol up)
2. Connect to pc and open console window as admin in folder with wheelie.exe and fastboot.exe and blobs.
3. Type
Code:
wheelie --blob blob.bin [enter]
4. When wheelie ramps up type
Code:
nvflash -r --download 4 bootloader.bct
5. When nvflash is successful reboot. You should be now in a bootloop on ASUS screen.
6. Reboot to bootloader (power+vol down).
7. You should now see the four icons: RCK, Andy, USB and wipe.
8. Press vol down to choose USB. Now tab should be recognized as fasboot device.
9. Unpack attached rar archive, rename content to simply 'blob' and put it in fastboot folder (it contains tf300t bootloader, apropriate partition table and 2.8.x.x. TWRP).
10. Fastboot blob using
Code:
fastboot -i 0x0b05 flash staging blob [enter]
fastboot -i 0x0b05 reboot [enter]
11. Let blue progressbar finish and tab reboot itself.
12. Now you should be on last tf300t bootloader with working TWRP and can flash whichever custom ROM you want. If you want to flash stock ROM and different TWRP, remember, that your tab is now effectively a tf300t, so flash ROMs and recoveries for tf300t.
Good luck!
Thanks for your answer,
das chaos said:
1. Put tab in apx mode (power + vol up)
2. Connect to pc and open console window as admin in folder with wheelie.exe and fastboot.exe and blobs.
3. Type
Code:
wheelie --blob blob.bin [enter]
Click to expand...
Click to collapse
When i type this, i have following message :
C:\fastboot>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d07877730060e
[=] RCM Version: 0x30001
[-] Error 3 receiving response from command
Click to expand...
Click to collapse
My tablet is detected by my computer as "ASus Transformer Prime APX Interface"...
orcad.fr said:
Thanks for your answer,
When i type this, i have following message :
My tablet is detected by my computer as "ASus Transformer Prime APX Interface"...
Click to expand...
Click to collapse
You never fail alone:
http://forum.xda-developers.com/showthread.php?t=2457624
Basic solution: Try another nvflash.exe: https://docs.google.com/file/d/0B20bCpM6OlP3eDlfVXdvMWMzdGM/edit
das chaos said:
You never fail alone:
http://forum.xda-developers.com/showthread.php?t=2457624
Basic solution: Try another nvflash.exe: https://docs.google.com/file/d/0B20bCpM6OlP3eDlfVXdvMWMzdGM/edit
Click to expand...
Click to collapse
Thanks for this link,
My tablet is alive! it's back to 4.1.1 stock...
I really want to go to F2FS system now... should i wait lillipop rom? KK thread is close...
what i've done using UN-BLOB'D STOCK JB 10.4.2.15 ROM :
C:\fastboot>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d07877730060e
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
C:\fastboot>nvflash.exe -r --download 4 blob.EBT
Nvflash v1.13.87205 started
[resume mode]
padded 3 bytes to bootloader
sending file: blob.EBT
/ 1558592/1558592 bytes sent
blob.EBT sent successfully
C:\fastboot>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d07877730060e
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
C:\fastboot>nvflash.exe -r --download 5 blob.SOS
Nvflash v1.13.87205 started
[resume mode]
sending file: blob.SOS
| 6183168/6183168 bytes sent
blob.SOS sent successfully
C:\fastboot>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d07877730060e
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
C:\fastboot>nvflash.exe -r --download 6 blob.LNX
Nvflash v1.13.87205 started
[resume mode]
sending file: blob.LNX
\ 5370112/5370112 bytes sent
blob.LNX sent successfully
C:\fastboot>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d07877730060e
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
C:\fastboot>nvflash.exe -r --download 10 blob.APP
Nvflash v1.13.87205 started
[resume mode]
sending file: blob.APP
/ 536870912/536870912 bytes sent
blob.APP sent successfully
Click to expand...
Click to collapse
Thanks again for saving my tablet !
orcad.fr said:
Thanks for this link,
My tablet is alive! it's back to 4.1.1 stock...
I really want to go to F2FS system now... should i wait lillipop rom? KK thread is close...
what i've done using UN-BLOB'D STOCK JB 10.4.2.15 ROM :
Thanks again for saving my tablet !
Click to expand...
Click to collapse
Are you now on 4.1.1 ICS stock or on 4.2.1 JB stock?
Read back the version of your bootloader! Three or four icons on bl screen?
das chaos said:
Are you now on 4.1.1 ICS stock or on 4.2.1 JB stock?
Read back the version of your bootloader! Three or four icons on bl screen?
Click to expand...
Click to collapse
When i boot with vol- i have 4 icons
and it's write :
Android cardhw-user bootloader (1.00 e) released by "US_epad-10.4.2.15-20120917" A803
Nb: RCK don't work, when i select it i have a dead android robot with red !
don't know which recovery i should install...
When it's boot, i have this informations :
Andoid
4.1.1
Noyau
3.1.10
[email protected]))
#1 SMP PREEMPT Mon Sep 17 15:39:42 CST 2012
Build
JEO03C.US_epad-10.4.2.15-20120917
Click to expand...
Click to collapse
orcad.fr said:
When i boot with vol- i have 4 icons
and it's write :
Android cardhw-user bootloader (1.00 e) released by "US_epad-10.4.2.15-20120917" A803
Nb: RCK don't work, when i select it i have a dead android robot with red !
don't know which recovery i should install...
When it's boot, i have this informations :
Click to expand...
Click to collapse
1. Of course you have dead android, because you flashed blob.SOS.
2. You are definitely on ICS bootloader, which is too old to flash the right TWRP.
You have the choice
1. Either download newest stock ROM for tf201 from ASUS support site and flash it via fastboot. From there you can flash proper TWRP.
2. Or you take my advice from post #6 and upgrade to tf300t bootloader. Then you can flash any custom ROM that is on the market.
das chaos said:
Any chance in the world! You are unbrickable (almost).
Follow this:
First you have to reset bootloader using wheelie routine:
1. Put tab in apx mode (power + vol up)
2. Connect to pc and open console window as admin in folder with wheelie.exe and fastboot.exe and blobs.
3. Type
Code:
wheelie --blob blob.bin [enter]
4. When wheelie ramps up type
Code:
nvflash -r --download 4 bootloader.bct
^ this command is wrong?
5. When nvflash is successful reboot. You should be now in a bootloop on ASUS screen.
6. Reboot to bootloader (power+vol down).
7. You should now see the four icons: RCK, Andy, USB and wipe.
8. Press vol down to choose USB. Now tab should be recognized as fasboot device.
9. Unpack attached rar archive, rename content to simply 'blob' and put it in fastboot folder (it contains tf300t bootloader, apropriate partition table and 2.8.x.x. TWRP).
10. Fastboot blob using
Code:
fastboot -i 0x0b05 flash staging blob [enter]
fastboot -i 0x0b05 reboot [enter]
11. Let blue progressbar finish and tab reboot itself.
12. Now you should be on last tf300t bootloader with working TWRP and can flash whichever custom ROM you want. If you want to flash stock ROM and different TWRP, remember, that your tab is now effectively a tf300t, so flash ROMs and recoveries for tf300t.
Good luck!
Click to expand...
Click to collapse
You really need to do your home work here if you're going to be giving advice .....
Hate to see someone brick a tablet cause you gave them the wrong command....
Nothing like downloading a bootloader to the partition table ....
Thx Josh
Code:
4. When wheelie ramps up type
Code:
nvflash -r --download 4 bootloader.bct
^ and so is this one ?
Click to expand...
Click to collapse
That's why i've try something else....
i don't have bootloader.bct file
i have to be sure now before trying again
lj50036 said:
You really need to do your home work here if you're going to be giving advice .....
Hate to see someone brick a tablet cause you gave them the wrong command....
Thx Josh
Click to expand...
Click to collapse
Second case I see my fault; apologize, but that wouldn't lead to a brick.
with
Code:
wheelie --blob blob.bin
I can't see any wrong.
@orcad.fr used it and obviously succeeded:
Code:
C:\fastboot>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d07877730060e
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
Click to expand...
Click to collapse
But you can take over if you think cryptic, elliptic and scornful comments can help any further.
das chaos said:
But you can take over if you think cryptic, eliptic and scornful comments can help any further.
Click to expand...
Click to collapse
Forgive me its late and I have had alot on my mind ....
Maybe edit your post as the correct command for that would be ....
Code:
nvflash -r --download 4 blob.EBT
.
Thx Josh
orcad.fr said:
That's why i've try something else....
i don't have bootloader.bct file
i have to be sure now before trying again
Click to expand...
Click to collapse
Sorry, @orcad.fr, that was a mistype, I thougt you would recognize quite easily:
I typed: 'bootloader.bct' (which is definitely wrong but you obviously do not have the file) and should have typed 'bootloader.ebt'. My bad; so follow @jl50036 - he is a master - if you can read his words.
Good bye
---------- Post added at 09:36 ---------- Previous post was at 09:35 ----------
jl50036 said:
Thinking about it for a min
Click to expand...
Click to collapse
Bluntly enough!
das chaos said:
Sorry, @orcad.fr, that was a mistype, I thougt you would recognize quite easily:
I typed: 'bootloader.bct' (which is definitely wrong but you obviously do not have the file) and should have typed 'bootloader.ebt'. My bad; so follow @jl50036 - he is a master - if you can read his words.
Good bye
---------- Post added at 09:36 ---------- Previous post was at 09:35 ----------
Bluntly enough!
Click to expand...
Click to collapse
I say im sorry and you just keep at it, such is life....
I am not the master of anything, just like to give correct info
Thx Josh
Keep cool every body!
I appreciate help, no matter who's giving.
Nobody's perfect (even me )
By the way, i've try with "bootloader.ebt" but it won't work, that's why i switched to the other solution.
If i take another rom from Asus, i must remobe blob or something like that?
I'll search a tutorial.
lj50036 said:
Forgive me its late and I have had alot on my mind ....
Maybe edit your post as the correct command for that would be ....
Code:
nvflash -r --download 4 blob.EBT
.
Thx Josh
Click to expand...
Click to collapse
Very right you are, but @orcad.fr wrote, that he had in his nvflash files a file bootloader.ebt (which I misspelled), wich cannot be anything else than blob.ebt even if he didn't succeed flashing this.
... and I, just like you, like to give correct info. If I fail - well after all I am human - I could be corrected, not cursed.
Related
[Q] CM7 works, CWM stuck on recovery key detected
So, I didn't flash this originally, and it still boots into CM7 just fine. ROM Manager is installed, it says CWM is successfully flashed and all, but any attempt to boot into recovery will just sit at "Recovery key detected. Booting recovery kernel image." Obviously the current ROM itself is actually working fine, so what would you suggest be my next step? Trying to put Flashback 10.3 on it. Current Recovery: 2.5.1.8 Current ROM: CyanogenMod-7.0.3-Harmony
1. Never use ROM Manager on the gTab. 2. You're on a 1.1 bootloader. Flashback is for 1.2 only. If you want HoneyComb for 1.1, try GtabCombOver or GtabComb. 3. To get CWM back, you'll have to use nvflash. Use bekit's original CWM 2.5.1.1-bekit-0.8 or CWM-4.0.1.5 images (ie. not the flashable zip files). See the OP in this thread for the nvflash cmd line to use.
Thanks for the advice. I'm just now coming to terms with this company not having a Micro-USB cable... >.<
Okay, so my screen is blank when in APX mode, it seems. I'm running NVFlash though, and I just have: Nvflash started _ It's been that way over an hour now. Tablet doesn't seem to be doing anything, neither does Command Prompt... just a blinking underscore. Canceled it... retried it... worked quickly (bootloader and recovery "sent succesfully", not sure why it hung up last time. Doesn't look like it's booting into recovery though, it's just hanging on the Viewsonic screen with the "Booting recovery kernel image" like before. Are you sure I have the 1.1 bootloader? Without stock, how can I tell?
ocdtrekkie said: Doesn't look like it's booting into recovery though, it's just hanging on the Viewsonic screen with the "Booting recovery kernel image" like before. Click to expand... Click to collapse What's the nvflash command you typed in and which recovery image did you flash? Are you sure I have the 1.1 bootloader? Without stock, how can I tell? Click to expand... Click to collapse Like this.
nvflash --bl bootloader.bin --download 9 recovery-clockwork-4.0.1.5-smb_a1002_bl1.1.img ^- that one. Not sure if I have a way to get a terminal emulator on this thing. And I don't have ADB here. Lemme see what I can manage.
That command line is correct. Put the tablet back into APX mode and run this command: Code: C:\> [B].\nvflash --bl bootloader.bin --format_partition 7 --format_partition 12 --go[/B] The ``--go'' flag will cause bootloader to try to boot into the ROM; otherwise it will just wait for further commands and you'll have to power off the tablet. If you lose the initial splash screen (the VS birds), then run the same command with a `6' instead of `7'.
Partitions formatted successfully, Go didn't seem to tell it to do anything, still had to turn it off. Still have birds, still won't boot into recovery. Command prompt paste: c:\Users\jweisz\Desktop\nvflash>nvflash --bl bootloader.bin --download 9 recover y-clockwork-4.0.1.5-smb_a1002_bl1.1.img Nvflash started rcm version 0X20001 System Information: chip name: t20 chip id: 0x20 major: 1 minor: 3 chip sku: 0x8 chip uid: 0x17144040411fa297 macrovision: disabled hdcp: enabled sbk burned: false dk burned: false boot device: nand operating mode: 3 device config strap: 0 device config fuse: 0 sdram config strap: 0 downloading bootloader -- load address: 0x108000 entry point: 0x108000 sending file: bootloader.bin | 928945/928945 bytes sent bootloader.bin sent successfully waiting for bootloader to initialize bootloader downloaded successfully sending file: recovery-clockwork-4.0.1.5-smb_a1002_bl1.1.img \ 3524608/3524608 bytes sent recovery-clockwork-4.0.1.5-smb_a1002_bl1.1.img sent successfully c:\Users\jweisz\Desktop\nvflash>.\nvflash --bl bootloader.bin --format_partition 7 --format_partition 12 --go Nvflash started rcm version 0X20001 System Information: chip name: t20 chip id: 0x20 major: 1 minor: 3 chip sku: 0x8 chip uid: 0x17144040411fa297 macrovision: disabled hdcp: enabled sbk burned: false dk burned: false boot device: nand operating mode: 3 device config strap: 0 device config fuse: 0 sdram config strap: 0 downloading bootloader -- load address: 0x108000 entry point: 0x108000 sending file: bootloader.bin | 928945/928945 bytes sent bootloader.bin sent successfully waiting for bootloader to initialize bootloader downloaded successfully Formatting partition 7 please wait.. done! Formatting partition 12 please wait.. done!
Questions: 1. Did the initial splash screen vanish? 2. Can you boot into the ROM? 3. What's the output of the ``dmesg | fgrep ...'' command? CM-7.0.3 should have everything you need to type that command in a Terminal Emulator window and find out the bootloader version.
CM7 has a terminal? Probably shoulda checked for that! LOL! Yeah, it's gotta be that I have 1.2 <7>[ 5.794813] Shmoo: s_CpuShmoo.ShmooVmaxIndex = 8
Alright, now I have recovery. See, you got me lost here: rajeevvp said: 2. You're on a 1.1 bootloader. Flashback is for 1.2 only. If you want HoneyComb for 1.1, try GtabCombOver or GtabComb. Click to expand... Click to collapse So... Flashback it is then, I guess.
Did you flash a customized CM-7.0.3 for the 1.2 bootloader because the standard one from cyanogenmod.com is 1.1 only? Anyway, nvflash the 1.2 version of CWM-4.0.1.5.
I didn't flash the CM7 that was on here. Couldn't tell you. Flashback works well on here. Thanks for all your help. Most of the time if I get a question reply from someone, they give one answer, then never come back to follow up. You're awesome.
ocdtrekkie said: I didn't flash the CM7 that was on here. Couldn't tell you. Click to expand... Click to collapse Then yours is a one-off. There are 1.2 versions of both CM-7.1.x and CM-7.2.x on the board here, but, I never encountered CM-7.0.3 on a 1.2 bootloader till today. Looks like somebody upgraded to the 1.2 bootloader and then flashed a 1.2 pershoot kernel before handing the tab over to you. Flashback works well on here. Thanks for all your help. Click to expand... Click to collapse Good luck with your new ROM.
[Q] Tf201 booting issue
Dear members, I have Asus Transformer Prime (TF 201). it was installed with V9.4.2.28 WW SKU (Android 4.0.3 ICS) i had rooted the machine and was working smoothly. i wanted to upgraded to V10.4.2.15 WW SKU (Android JB 4.1.1) and i did upgraded prior running any apk for root keeping. once it was upgraded i was not able to root it aging. i searched the web and found a fastboot command like fastboot erase system, erase recovery and ..... i run these commands and found that everything is gone. lately i uploaded some img (rtr_recovery-clockwork-touch-5.8.1.8-tf201.zip) in recovery partition. now i can only go in apx mode, i can not get it to run on fastboot mode. can anyone help me in this regards, your comments and guidance are highly appreciated. Regards, AICTS
can some one help me with apx mode, when i run nvflash it give below issue: bct transformer.bct --bl bootloader.bin --odm 0x300d8011 Wheelie 0.1 - Preflight for nvflash. Copyright (c) 2011-2012 androidroot.mobi ======================================== Using SBK type 2. Using bootloader: 'bootloader.bin'. Using BCT: 'transformer.bct'. ---------------------------------------- [=] Chip UID: 0x98243045304833030 [-] Incorrect SBK or SBK type selected. nverror: 0x4. C:\Users\Hameed\Downloads\bee\BRK_RootKit_v8.0_final\tmpboot>"nvflash.exe" -r -- bct transformer.bct --setbct --configfile flash.cfg --create --odmdata 0x300d801 1 --sync Nvflash started [resume mode] failed executing command 11 NvError 0x30012 command failure: create failed C:\Users\Hameed\Downloads\bee\BRK_RootKit_v8.0_final\tmpboot>"nvflash.exe" -r -- go Nvflash started [resume mode]
[Q] Help! I think I broke APX mode! (TF201)
Hi, In the middle of nvflashing my TFPrime, the power went out and now my tablet no longer shows the ASUS logo. It is just a Black screen, and I can only go into APX mode. On entering APX mode and running sudo sh wheelie --blob blob.bin I get the following error Waiting for device in APX mode... [=] Chip UID: 0x_____________ [=] RCM Version: 0x30001 [=] CPU Model: Tegra 3 [+] Sending bootloader... [-] Error 3 sending command It will not recieve the APX bootloader, and now I think my device is perma-bricked. My PC is running: UbuntuGnome 13.10 x64 Im using the blobs i extracted from my device and am using the official AndroidRoot.mobi Linux Binaries Please Help, AirborneRadio
Try running wheelie with the -r option. wheelie -r --blob blob.bin Sent from my SO-04E using xda app-developers app
kokopuphz said: Try running wheelie with the -r option. wheelie -r --blob blob.bin Sent from my SO-04E using xda app-developers app Click to expand... Click to collapse What does the "-r" argument do? I am attempting to revive my TF300T from the notorious Error 3 as well.
Need help with APX mode
Hello,
I tried to flash Android 4.4 with an updated version of TWRP.
Once the installation was done, my tab hangs at the bootscreen.
I'm seeing the asus logo, but without the text "This device is unlocked"
Lucky me, i have the NVflash, and the blobs.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and the imgs
Also i'm able to get in the APX mode
Code:
D:\Tablet Brick safe\tf201_nvflashpack>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d07875164040c
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
So what should i do next?
Thanks dor the help.
brantje said: So what should i do next? Thanks dor the help. Click to expand... Click to collapse http://forum.xda-developers.com/showthread.php?t=1927818 And boom goes the dynamite..
wickid_d said: http://forum.xda-developers.com/showthread.php?t=1927818 And boom goes the dynamite.. Click to expand... Click to collapse If I don't have blob.bin, can I unbrick my tf201 ? How can I get this file ?
darkjeff said: If I don't have blob.bin, can I unbrick my tf201 ? How can I get this file ? Click to expand... Click to collapse With the lack of information, I'll tell you it depends on the kind of brick. If it's a soft brick and you still have access to the fastboot menu, yes, but if it's a hard brick to where you don't have that access, no. Your blob.bin is exclusive to your board, and you have to go through the nvflash process to get it. It's kind of like a fingerprint. I've even contacted one of the nvidia developers about it before replacing my board. I hope that clarifies things a little.
wickid_d said: With the lack of information, I'll tell you it depends on the kind of brick. If it's a soft brick and you still have access to the fastboot menu, yes, but if it's a hard brick to where you don't have that access, no. Your blob.bin is exclusive to your board, and you have to go through the nvflash process to get it. It's kind of like a fingerprint. I've even contacted one of the nvidia developers about it before replacing my board. I hope that clarifies things a little. Click to expand... Click to collapse I updated CM but it did not boot on. I has access to fastboot but no more after reboot. I don't know why now my tab is in loop boot.
darkjeff said: I updated CM but it did not boot on. I has access to fastboot but no more after reboot. I don't know why now my tab is in loop boot. Click to expand... Click to collapse Have you tried using adb to reboot to it? 'adb reboot-bootloader'? Even if CM (or any rom, for that matter) is just barely starting to boot, you should be able to do this. Once you get to fastboot, follow this guide: https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/ And then follow the guide in my previous post in this thread and that will at the very least get you back to stock. And remember, whenever you flash something in fastboot, no matter what it is, use the option '-i 0x0b05'.. Like for recovery 'fastboot -i 0x0b05 flash recovery (name of recovery here)' This will save you more headaches.
Trouble with generating blob.bin with Flatline_tf201.img / CWM Moved to proper thread
brantje said: Hello, I tried to flash Android 4.4 with an updated version of TWRP. Once the installation was done, my tab hangs at the bootscreen. I'm seeing the asus logo, but without the text "This device is unlocked" Lucky me, i have the NVflash, and the blobs. So what should i do next? Thanks dor the help. Click to expand... Click to collapse Did you solve it? I think i am in same trouble.
vanquishe said: Did you solve it? I think i am in same trouble. Click to expand... Click to collapse Mot yet l. Will look into it this weekend. Quite busy with work. Sent from my SM-N9005 using Tapatalk
I am in the same fix. Here is what I did so far. I hope someone can provide some advice. 1. Stock JB, newest from OTA, untouched (im from japan, so i think its a JP SKU) 2. Followed guide to unlock + backup blobs + enable nvflash for JB http://matthill.eu/android/transformer-prime-tf201-jellybean-nvflash/ 3. Rooted with motochopper 4.Followed guide to install: [ROM][4.4.2 CM-11.0][Cyanogenmod 11.0 Unofficial][KOT49H][20/02/14] http://forum.xda-developers.com/showthread.php?t=2589554 4.1 Downloaded and transfer following files to sdcard folder cm-11-20140220-UNOFFICIAL-tf201 pa_gapps-modular-mini-4.4.2-20140227-signed 4.2 Downloaded recovery.img.SOS 2013-12-29 08:42 http://forum.xda-developers.com/devdb/project/?id=2229#downloadsfastboot -i 0xb05 flash recovery recovery.img.SOS 4.3 fastboot -i 0xb05 flash recovery recovery.img.SOS (I did notice it was 0xb05 and not 0x0b05 but i copied paste exactly) 4.4 restart TF, "power+down", select RCK 4.5 Did the following in recovery menu: a. Backup, but did it to sdcard instead of ext storage b. wipe data/factory c. wipe cache partition d. wip dalvik cache e. install zip: cm-11-20140220-UNOFFICIAL-tf201 f. install zip: pa_gapps-modular-mini-4.4.2-20140227-signed At step f, the screeen said somthing about insufficient space. So i thought i would try without GAPPS and selected reboot system now. 5. Got stuck at Asus word in middle of screen a. Bottom right shows "Powered by nvidia terga" b. Oddly, top left no longer displays "device is unlocked" 6. Tried to reboot (holding power long time) a. Screen black out, vibrate b. Tried to get to fastboot (power + down) but the icons never show c. Constantly stuck with Asus screen 7. Attempted to follow guide: [GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201 http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash a. "Power + up", apx device shows in windows 7 device manager b. wheelie.exe --blob blob.bin c. nvflash.exe -r --download 4 bootloader.EBT (bootloader.ebt is the output i got previously from flatline) (my bootloader.ebt is 1,558,608 bytes) (blob.edt from TF201-JB-10.4.2.15-Unblobed is 1,558,589 bytes) d. This is the log log: C:\nvflash>nvflash.exe -r --download 4 bootloader.ebt Nvflash v1.13.87205 started [resume mode] sending file: bootloader.ebt bootloader.ebt sent successfully e. Device went black screen, device manager does not show APX f. I power the device up but shows black screen. "power + down" still does not work. g. However, "power + up" still get APX device in windows. ---------- Post added at 10:40 AM ---------- Previous post was at 09:51 AM ---------- Im thinking I could try either of the following: Option 1: 1. Follow this [GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201 http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash but use the boot.ebt from TF201-JB-10.4.2.15-Unblobed and try to go as far as I can and pray for the best (what puzzles me is that instructions dun seem to have anything to do with the unlock-token.img,bricksafe.img,factory-config.img) Option 2: 1. Follow this [NvFlash] [Recovery] With [Generated Blobs][TF300T] http://forum.xda-developers.com/showthread.php?p=48948717&highlight=bricksafe+img#post48948717 seems to talk about unlock-token.img,bricksafe.img,factory-config.img but it is for tf300T also, i have no idea how to get the following file "this is how we got around it.download the correct .blob from TWRP rename it twrp.blob then run "Code: nvflash -r --download 5 twrp.blob" Option 3: 1. Sit and wait for help... no one on MIRC seems to be responding T T Any ideas?
vanquishe said: I am in the same fix. Here is what I did so far. I hope someone can provide some advice. Any ideas? Click to expand... Click to collapse Ok, first off, it IS 0x0b05.. 0b05 is the vendor/hardware hexadecimal ID number, which is why -i (short for ID) when using fastboot. You can verify this by hooking the tablet up to a linux environment and running 'lsusb' in terminal and looking for the Asus line. In Windows, I'm not exactly sure why the 0x gets added at the front. I guess it's just how Windows handles hardware IDs. (source: https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/ part: (Please note that for transformer tablets the fastboot command might require the option "-i 0x0b05".)) Second, you won't be able to install the full PA Gapps along with CM11 - you're right, there isn't enough room. Use either the micro or mini package. This is talked about in the CM11 thread you mentioned, where I have been frequenting, as of late. Third, and finally, what exactly are you waiting on? You've done everything correctly as far as I can tell. Just start the process over with reinstalling stock via this guide: http://forum.xda-developers.com/showthread.php?t=1927818 and you can either flash TWRP through nvflash mode like you did (good job on that ), or via fastboot, and go from there. Whether it shows 'this device is unlocked' or not, at this point, shouldn't matter.. You've run through the nvflash process and created your blob.bin along with the other files. I hope this helps.
Hi Mates, Will start looking into it now. As long i can get TWRP i'm happy, because then i i'm not far from installing a custom rom. 14:55 - Tablet was empty its charging now 16:27 - I'm screwd i think... D:\Downloads\Tablet Brick safe\Tablet Brick safe\tf201_nvflashpack>wheelie.exe - -blob blob.bin Wheelie 0.1 - Preflight for nvflash. Copyright (c) 2011-2012 androidroot.mobi ======================================== Waiting for device in APX mode... [=] Chip UID: 0x15d07875164040c [=] RCM Version: 0x30001 [-] Error 3 receiving response from command Will keep this post updated about my progress.
vanquishe said: I am in the same fix. Here is what I did so far. I hope someone can provide some advice. 1. Stock JB, newest from OTA, untouched (im from japan, so i think its a JP SKU) 2. Followed guide to unlock + backup blobs + enable nvflash for JB http://matthill.eu/android/transformer-prime-tf201-jellybean-nvflash/ 3. Rooted with motochopper 4.Followed guide to install: [ROM][4.4.2 CM-11.0][Cyanogenmod 11.0 Unofficial][KOT49H][20/02/14] http://forum.xda-developers.com/showthread.php?t=2589554 4.1 Downloaded and transfer following files to sdcard folder cm-11-20140220-UNOFFICIAL-tf201 pa_gapps-modular-mini-4.4.2-20140227-signed 4.2 Downloaded recovery.img.SOS 2013-12-29 08:42 http://forum.xda-developers.com/devdb/project/?id=2229#downloadsfastboot -i 0xb05 flash recovery recovery.img.SOS 4.3 fastboot -i 0xb05 flash recovery recovery.img.SOS (I did notice it was 0xb05 and not 0x0b05 but i copied paste exactly) 4.4 restart TF, "power+down", select RCK 4.5 Did the following in recovery menu: a. Backup, but did it to sdcard instead of ext storage b. wipe data/factory c. wipe cache partition d. wip dalvik cache e. install zip: cm-11-20140220-UNOFFICIAL-tf201 f. install zip: pa_gapps-modular-mini-4.4.2-20140227-signed At step f, the screeen said somthing about insufficient space. So i thought i would try without GAPPS and selected reboot system now. 5. Got stuck at Asus word in middle of screen a. Bottom right shows "Powered by nvidia terga" b. Oddly, top left no longer displays "device is unlocked" 6. Tried to reboot (holding power long time) a. Screen black out, vibrate b. Tried to get to fastboot (power + down) but the icons never show c. Constantly stuck with Asus screen 7. Attempted to follow guide: [GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201 http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash a. "Power + up", apx device shows in windows 7 device manager b. wheelie.exe --blob blob.bin c. nvflash.exe -r --download 4 bootloader.EBT (bootloader.ebt is the output i got previously from flatline) (my bootloader.ebt is 1,558,608 bytes) (blob.edt from TF201-JB-10.4.2.15-Unblobed is 1,558,589 bytes) d. This is the log log: C:\nvflash>nvflash.exe -r --download 4 bootloader.ebt Nvflash v1.13.87205 started [resume mode] sending file: bootloader.ebt bootloader.ebt sent successfully e. Device went black screen, device manager does not show APX f. I power the device up but shows black screen. "power + down" still does not work. g. However, "power + up" still get APX device in windows. ---------- Post added at 10:40 AM ---------- Previous post was at 09:51 AM ---------- Im thinking I could try either of the following: Option 1: 1. Follow this [GUIDE] nvFlash General Users Guide [Unbrick/Recover/Downgrade/Upgrade]- TF201 http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash but use the boot.ebt from TF201-JB-10.4.2.15-Unblobed and try to go as far as I can and pray for the best (what puzzles me is that instructions dun seem to have anything to do with the unlock-token.img,bricksafe.img,factory-config.img) Option 2: 1. Follow this [NvFlash] [Recovery] With [Generated Blobs][TF300T] http://forum.xda-developers.com/showthread.php?p=48948717&highlight=bricksafe+img#post48948717 seems to talk about unlock-token.img,bricksafe.img,factory-config.img but it is for tf300T also, i have no idea how to get the following file "this is how we got around it.download the correct .blob from TWRP rename it twrp.blob then run "Code: nvflash -r --download 5 twrp.blob" Option 3: 1. Sit and wait for help... no one on MIRC seems to be responding T T Any ideas? Click to expand... Click to collapse Exact same boat, so will try and look for answers now. Where on mirc, maybe we can help each other.
I will just sit quietly here and wait for anyone with an answer. (Yes, me too) vanquishe said: (what puzzles me is that instructions dun seem to have anything to do with the unlock-token.img,bricksafe.img,factory-config.img) Click to expand... Click to collapse Yes, that. I would like to write more, but you have actually posted what I did. However, I found a hint in a thread where someone hat a wheelie that did not work, and another version that did. Unfortunately, I was slightly drunk and cannot find it anymore.
Xerxes-3.0 said: I will just sit quietly here and wait for anyone with an answer. (Yes, me too) Yes, that. I would like to write more, but you have actually posted what I did. However, I found a hint in a thread where someone hat a wheelie that did not work, and another version that did. Unfortunately, I was slightly drunk and cannot find it anymore. Click to expand... Click to collapse I had help from a nice person from IRC. Now my TF201 is up and running again. I will up the process he guided me once I get home later.
Please thank lj50036 from the CMB team. It was him that guided me thru the process to unbrick my TP. ----------------------------------------------- Bricked situation: 1. Last activity before brick: Stock with latest OTA -> Flatline (OK) -> Motochopper (OK) -> Flash CWM recovery (OK) -> Unofficial CM11 (Reboot = bricked) 2. Stuck at ASUS logo on power up/reboot. (Device is unlocked no longer shows on top left corner) 3. Cannot get to fastboot (power + dwn = stuck at ASUS logo) 4. However, can invoke APX mode (power + up = APX device detects in windows) ----------------------------------------------- Preparation: 1. All the output files from the flatline (blob.bin, unlock-token, bricksafe, factory-config etc) 2. Fastboot,adb,nvflash exe (you should have all these when you did flatline) 3. Enough battery (I left it overnight to charge, since I had no way of checking batt) 4. The stock firmware from ASUS (you should get the same version as the one you had prior to brick) ----------------------------------------------- Actual process: 1. I was told to put all the files from fastboot,nvflash etc in C root (ie .exe,.img,.dlls, bin etc). I think it is not a must, as long as you have all the files together and dir has no spaces. 2. Unzip the firmware file from ASUS. My case: the file name is JP_epaduser_10_4_2_18UpdateLauncher, extracted to find JP_epad-user-10.4.2.18. Extract again to find a file called Blob, which is about 500mb. 3. Copy the blob file to C root 4. Open CMD as admin. Make sure you do so as admin. 5. Goto C root, type: cd\ 6. Just make sure you can execute the following exe: fastboot, adb, nvflash, type: fastboot The commands should output the help related info....ie parameters etc 7. Now boot you tablet into apx conneted to your pc from tablet to pc no hubs docks> Device manager shows Asus tranformer prime APX interface. 8. Type: wheelie --blob blob.bin My output: C:\>wheelie --blob blob.bin Wheelie 0.1 - Preflight for nvflash. Copyright (c) 2011-2012 androidroot.mobi ======================================== Waiting for device in APX mode... [=] Chip UID: 0x15c7d7a49042111 [=] RCM Version: 0x30001 [=] CPU Model: Tegra 3 [+] Sending bootloader... Sending file: 100 % [!] Done - your device should now be ready for nvflash My tablet screen shows: top left: entering nvflash recovering mode / nv3p server chip uid: 015c7d7a49042111 center: Asus bottom right owr by... 9. Now it may reboot at the end of this just get back to apx mode on your tablet. Type: nvflash -r --download 7 unlock-token.img Output: C:\>nvflash -r --download 7 unlock-token.img Nvflash v1.13.87205 started [resume mode] sending file: unlock-token.img unlock-token.img sent successfully *My device black out. So i rebooted to APX again as instructed. 10. Type: wheelie --blob blob.bin 11. Type: nvflash -r --download 14 factory-config.img Output: C:\>nvflash -r --download 14 factory-config.img Nvflash v1.13.87205 started [resume mode] sending file: factory-config.img factory-config.img sent successfully *My device black out. So i rebooted to APX again as instructed. An did wheelie again 12. Type: nvflash -r --rawdevicewrite 0 2944 bricksafe.img Output: C:\>nvflash -r --rawdevicewrite 0 2944 bricksafe.img Nvflash v1.13.87205 started [resume mode] sending file: bricksafe.img bricksafe.img sent successfully *device did not blackout this time. So no need to reboot. 13. Type: nvflash -r --go Output: C:\>nvflash -r --go Nvflash v1.13.87205 started [resume mode] 14. Power + DWN to try to get to fastboot. Select the USB icon. *windows device manager should detect fast boot interface *confirm this by typing: fastboot devices *my output was: 015c7d7a49042111 fastboot 15. Type: fastboot erase system Output: C:\>fastboot erase system ******** Did you mean to fastboot format this partition? erasing 'system'... OKAY [ 2.671s] finished. total time: 2.671s 16. Type: fastboot erase recovery Output: C:\>fastboot erase recovery erasing 'recovery'... OKAY [ 1.929s] finished. total time: 1.929s 17. Type: fastboot -w Output: C:\>fastboot -w erasing 'userdata'... OKAY [ 50.110s] formatting 'userdata' partition... Creating filesystem with parameters: Size: 61980278784 Block size: 4096 Blocks per group: 32768 Inodes per group: 8192 Inode size: 256 Journal blocks: 32768 Label: Blocks: 15131904 Block groups: 462 Reserved block group size: 1024 Created filesystem with 11/3784704 inodes and 283616/15131904 blocks sending 'userdata' (141195 KB)... Created filesystem with 11/3784704 inodes and 283616/15131904 blocks sending 'userdata' (141195 KB)... writing 'userdata'... OKAY [ 26.179s] FAILED (command write failed (Unknown error)) finished. total time: 76.878s *dont be bothered by the error 18. Type: fastboot devices Output: C:\>fastboot devices ???????????? fastboot 19. Reboot and get back to fastboot again, check that your device is detected by Type: fastboot devices Output: C:\>fastboot devices 015c7d7a49042111 fastboot 20.fastboot erase boot Output: C:\>fastboot erase boot erasing 'boot'... OKAY [ 1.874s] finished. total time: 1.874s 21.Type: fastboot erase misc Output: C:\>fastboot erase misc erasing 'misc'... OKAY [ 0.978s] finished. total time: 0.978s 22. Type: fastboot erase cache Output: C:\>fastboot erase cache ******** Did you mean to fastboot format this partition? erasing 'cache'... OKAY [ 1.713s] finished. total time: 1.713s 23. Next cmd takes long time. Type: fastboot -i 0x0B05 flash system blob * During the writing process of this step you will get the blue bar on your screen..... Output: C:\>fastboot -i 0x0B05 flash system blob erasing 'system'... OKAY [ 2.225s] sending 'system' (537604 KB)... OKAY [ 90.363s] writing 'system'... OKAY [130.010s] finished. total time: 222.600s 24. Type: fastboot -i 0x0B05 reboot *this reboot should bring you to stock rom *will take some time, just be patient *does not matter if you have usb connected or not ----------------------------------------------- If you reach here, you should have a fresh TP with stock, except its unlocked. Hope this helps.
This is great, thank you. I actually wanted to do this yesterday evening when i found out that the prime has run out of battery (because I'm a genius), but I will do this today.
Ok, it did not work from scratch, but then, I had already another ROM so I made things difficult. With your checklist, I got to step 13, but still only APX mode. So i did some guessing work. What I did (in short, assuming I have everything till your step 7 and doing the wheelie everytime): a) nvflash -r --download 4 bootloader.ebt b) nvflash -r --download 7 unlock-token.img c) nvflash -r --download 5 recovery.img.SOS (the modified CWM from namidairo for his unofficial CM11) d) nvflash -r --rawdevicewrite 0 2944 bricksafe.img (no wheelie afterwards) e) nvflash -r --go Now I DO have the option for fastboot but no recovery (unrecoverable boot loader error). Will continue frfom here. === Next: Another bootloader. I tried the blob.EBT from the stock ROM and with this, it actually tries to boot by itself (showing "device is unlocked"). === Fine. I repeated wheelie and step c), got the blue bar, now I have thew modified CWM v6.0.4.5. Running. Yay me. Okay, after one try with CM11 ended me where I was starting, I came back to CWM with step a) and b), and now I'm going to bed.
I am stupid and skipped flashing the stock ROM. Stupid me. Now it works. Weee! Did I say thank you? I think just one time. Thank you for posting thes extrensive get-youself-out-of-the-dirt-manual.
This thread has the most important info for the TFP I've seen. This info should be shared out to the Brick recovery thread (and linked to the custom ROM threads)! I've been thinking of moving from Androwook to CM11, and the only way I would try it is with a really good grasp on recovering the blob files. So again thanks, this is now bookmarked to my favorites. And especially a huge thanks to Xerxes-3.0 and vanquishe. You both just saved me from my future brick!
[Q] loading Wheelie stops on 100%
Hi. I made NVflash on android 4.1 then I flash 4.2 ROM When I tryed to unbrick my ASUS TF pad through NVflash I downgrade the bootloader and after it pad don't work (here's the bootloader 4.1 and recovery 4.2) and when I try to unrbrick APx loading stops on Wheelie 0.1 - Preflight for nvflash. Copyright (c) 2011-2012 androidroot.mobi ======================================== Waiting for device in APX mode... [=] Chip UID: 0x15c7d7a681fec0f [=] RCM Version: 0x30001 [=] CPU Model: Tegra 3 [ ] Sending bootloader... Sending file: 100 % I try to use Wheelie 0.2 but it's don't work with 4.1 blob Does anyone have any ideas?
Bogdan_97ua said: Hi. I made NVflash on android 4.1 then I flash 4.2 ROM When I tryed to unbrick my ASUS TF pad through NVflash I downgrade the bootloader and after it pad don't work (here's the bootloader 4.1 and recovery 4.2) and when I try to unrbrick APx loading stops on Wheelie 0.1 - Preflight for nvflash. Copyright (c) 2011-2012 androidroot.mobi ======================================== Waiting for device in APX mode... [=] Chip UID: 0x15c7d7a681fec0f [=] RCM Version: 0x30001 [=] CPU Model: Tegra 3 [ ] Sending bootloader... Sending file: 100 % I try to use Wheelie 0.2 but it's don't work with 4.1 blob Does anyone have any ideas? Click to expand... Click to collapse What is your PC OS ? What is the command you are using ? How did you downgrade the bootloader ? Thx Josh
lj50036 said: What is your PC OS ? What is the command you are using ? How did you downgrade the bootloader ? Thx Josh Click to expand... Click to collapse On my PC are Win 8.1; XP; and Ubuntu and everywhere the same I use wheelie --blob blob.bin ( with wheelie -r --blob blob.bin happens nothing) nvflash -r --download 4 blob.EBT and after I entered this command and pad rebooted I can't do anything
lj50036 said: What is your PC OS ? What is the command you are using ? How did you downgrade the bootloader ? Thx Josh Click to expand... Click to collapse Do you know how I can repair it?