Ok so my N1 is unlocked and is running CM ROMs fine i just do not have adb. ADB worked great back when CM was in beta but not it isn't working anymore. What i wanted to do last night was to do a fastboot erase XXX. XXX being boot/system/data. Only thing is that every time i try to do that command i get a Fastboot remote: Not allowed. If i try and flash over something using fastboot i get a Fastboot remote: unknown Error. I know my phone is connected because fastboot devices shows my phone. I am just wondering what could be causing this and how i can go about fixing it. Thanks for any help.
The last time I saw that error was when my service provider pushed a locked SPL in an update that rendered fastboot unusable.
This can't be a problem in Nexus though. Are you sure you see a big pink "UNLOCKED" at the very top of your bootloader?
Oh its there, it says unlocked on top of the bootloader as well as having the lock on the boot screen. I was hoping that by erasing and flashing the system and boot would fix adb. I have had this problem ever since CM moved to the larger boot.img files. I just don't get what it is. The phone flashes every thing fine under recovery but fastboot just doesn't work and adb only works within recovery not in the Rom.
Well that's really weird. Have you tried uninstalling the phone drivers from your computer and installing SDK from scratch?
have you found a solution? I have the same problem. remote not allowed. I also have a rootet n1 on the top a pink font with UNLOCKED.
fastboot erase system -w
Hello,
actually ive got the same problem. Coming from Nightly Build (27.08.2010) and want to flash the CM6.0 (Final).
Nexus is staying in a bootloop and a fullwipe with RA doesnt make it possible to boot the CM6.0.
So i forwarded the problem as an issue to the CM Dev. He recommended to clear the System with :
fastboot erase system -w
erasing 'system'... FAILED (remote: not allowed)
finished. total time: 0.066s
I have the same issue. I'm thinking maybe this is why I can't flash CM6 properly. I run adb logcat and I just get a loop.
PlusOne3k said:
Hello,
actually ive got the same problem. Coming from Nightly Build (27.08.2010) and want to flash the CM6.0 (Final).
Nexus is staying in a bootloop and a fullwipe with RA doesnt make it possible to boot the CM6.0.
So i forwarded the problem as an issue to the CM Dev. He recommended to clear the System with :
fastboot erase system -w
erasing 'system'... FAILED (remote: not allowed)
finished. total time: 0.066s
Click to expand...
Click to collapse
exactly the same problem here.. any ideas?
Did any of you use the One-Click root method (or Unrevoked)?
That installs a custom usb driver that may not work properly with fastboot.
If this is the case, remove that driver and replace it with the one from the SDK...
May work... ?
I unlocked the Nexus One with fastboot oem unlock.
Did not use the "one click" method, using the Android SDK USB Drivers.
Other Option : Tried to format the "System" with Clockwork Orange Recovery - still got the bootloop.
D/AndroidRuntime( 198):
D/AndroidRuntime( 198): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
I/AndroidRuntime( 198): Heap size: -Xmx16m
D/AndroidRuntime( 198): CheckJNI is OFF
D/dalvikvm( 198): creating instr width table
D/dalvikvm( 198): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 198): Stale deps in cache file; removing and retrying
W/dalvikvm( 198): Size mismatch on inflated file (1375125 vs 1376936)
E/dalvikvm( 198): Unable to extract+optimize DEX from '/system/framework/services.jar'
D/dalvikvm( 198): Unable to process classpath element '/system/framework/services.jar'
D/AndroidRuntime( 198): --- registering native functions ---
E/JNIHelp ( 198): Native registration unable to find class 'com/android/server/Watchdog'
E/AndroidRuntime( 198): Unable to register all android natives
Click to expand...
Click to collapse
Best regards, Alex.
PlusOne3k said:
I unlocked the Nexus One with fastboot oem unlock.
Did not use the "one click" method, using the Android SDK USB Drivers.
Other Option : Tried to format the "System" with Clockwork Orange Recovery - still got the bootloop.
Best regards, Alex.
Click to expand...
Click to collapse
Wow... are you trying to use a theme on a stock rom? That's a totally corrupt rom there...
Edit, just read back a bit... have you tried formatting /system and /data in recovery?
I havent had this problem in along time. it turned out that the boot.img file wasn't flashing right so fastboot and adb didn't work. Once i got a rom with a working boot.img the problem was gone. As of right now i am running the latest CM6 with no problems at all. I am not sure about everyone elses problems sry. Other wise a I am good to go so if the thread is not needed about the problem a Mod can lock it.
Sure, i tried to format with Clockwork Orange Recovery.
Same result like before.
I tried "Clear Storage" from the Bootloader, after this i started the RA Recovery 1.8 and wiped all necessary Stuff. (Cache/Data/DalvikVM)
- Flashed CM6.0
- Flashed Gapps.
..... same result :/
** News : I visited the MoDaCo Kitchen, where you can cook the CM6.0 Final Release ! Guess what? Its working now, without "wipe" or anything.
Best regards, Alex.
My Nexus One is rooted by the universal androot.
I unrooted, but it still doesn't work.
Still No Allow
I Look many places but cant find a solution.
I have an:
Sapphire PVT 32A SHIP S-ON H
HBOOT-1.76.0010 (SAPP60000)
CPLD-12
RADIO-6.35.16.19
I tried install many rooms, many spl, radios, boots and recoverys.
The rom not work and not show progress, the others show the message "Remote Not Allow"
Somebody give me a tip?
-------------
I see before a post the mistake, i'll ask in the right forum sorry.
Thanks
That's because you have an S-ON bootloader, try asking about it in the HTC Magic forums.
Related
Hey guys,
Been beating my head against this for weeks. (see the history of my lament here http://forum.xda-developers.com/showthread.php?t=597987)
This all happened after I installed Android 2.0 EOSP and death SPL.
I'm unable flash new roms, I get the below error loop (see code) whenever I try and install cyanogen mod (yes I'm doing it properly as I've done it 30 times before).
I've tried a goldcard.
I've tried all the perfected SPL tricks outlined here to no avail (http://forum.xda-developers.com/showthread.php?t=570659 &
http://forum.xda-developers.com/showthread.php?t=529019)
I've tried:
Engineering SPL 1.33.2010
Engineering SPL 1.33.2009
Engineering SPL 1.33.2005
Engineering SPL 1.33.2004
Engineering SPL 1.33.2004 by Crios
The only two things I can do are restore 1 single nandroid (I have like 6, only one works) or sappimg.nbh.
My phone is a MT3G, it IS rooted.
Amon RA recovery image 1.5.2G
SAPPHIRE PVT 32B ENG S-OFF H
HBOOT-1.33.2004 (SAPP30000)
CPLD-10
RADIO-2.22.19.26I
Code:
D/AndroidRuntime( 145): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 145): CheckJNI is OFF
D/dalvikvm( 145): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 145): Stale deps in cache file; removing and retrying
W/dalvikvm( 145): Size mismatch on inflated file (5592188 vs 5595128)
E/dalvikvm( 145): Unable to extract+optimize DEX from '/system/framework/framework.jar'
D/dalvikvm( 145): Unable to process classpath element '/system/framework/framework.jar'
D/AndroidRuntime( 145): --- registering native functions ---
E/JNIHelp ( 145): Native registration unable to find class 'android/debug/JNITest'
E/AndroidRuntime( 145): Unable to register all android natives
Any ideas?
wow im impressed you tried every SPL in the book and havent bricked your phone lol.
anyway the best SPL for mytouch 3g is 1.33.2005, make sure its the engineering SPL (This one)
then try flashing a rom again.
also it would help to post the info on your bootloader menu ( all the stuff on top)
melterx12 said:
wow im impressed you tried every SPL in the book and havent bricked your phone lol.
anyway the best SPL for mytouch 3g is 1.33.2005, make sure its the engineering SPL (This one)
then try flashing a rom again.
also it would help to post the info on your bootloader menu ( all the stuff on top)
Click to expand...
Click to collapse
I've tried that SPL as well, also I did post the stuff on top although it'll vary from SPL to SPL
SAPPHIRE PVT 32B ENG S-OFF H
HBOOT-1.33.2004 (SAPP30000)
CPLD-10
RADIO-2.22.19.26I
So far EVERYTHING I've tried other than sappimg.nbh Or one of my nandroid restores, I get the boot error loop that I listed above.
well install the 2005 spl to be sure, go into recovery, wipe data, format sd card, and flash a fresh rom.
I did that after your post. Still get the same error.
Any other ideas?
I also tried this with a brand new SD card.
Potato potato
i get the same problem, kingskilck 2.1 works but not much else besides, If anyone has any ideas please help!!!
D/dalvikvm( 620): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 620): Stale deps in cache file; removing and retrying
W/dalvikvm( 620): Size mismatch on inflated file (6099448 vs 6103980)
E/dalvikvm( 620): Unable to extract+optimize DEX from '/system/framework/framew
ork.jar'
D/dalvikvm( 620): Unable to process classpath element '/system/framework/framew
ork.jar'
D/AndroidRuntime( 620): --- registering native functions ---
E/JNIHelp ( 620): Native registration unable to find class 'android/debug/JNITe
st'
E/AndroidRuntime( 620): Unable to register all android natives
I/ServiceManager( 164): service 'media.audio_flinger' died
I/ServiceManager( 164): service 'media.player' died
I/ServiceManager( 164): service 'media.camera' died
I/ServiceManager( 164): service 'media.audio_policy' died
Forget it....
no idea if this will work, but it won't do any harm to clear cache
( I see no mention of it above )
if you haven't already use the wipe dalvik-cache option in RA-1.5.2 ( or current version ) and reboot ( back button and choose option )
if you have tried this then try manually
drop to recovery console
Code:
mount /cache
rm /cache/dalvik-cache/*
if you get errors post them here
if not reboot
Code:
reboot
if that doesn't work...
go back into recovery
use all of the wipe options ( data/factory, dalvik-cache, sd:ext )
reflash, reboot
if that doesn't work I tried my best, but no harm in posting any observations you may have made while trying
"When the DEX file is created, the file header is first filled with
0xff. Then the rest of the file is written, and finally the header is
written. So, the "incorrect opt magic number" message just means that
a previous run of dexopt failed before the file was completely
written.
What you need to be looking at is the segmentation fault in dexopt.
You've broken something in the VM"
Just got this on google groups, does anyone know what this means?
Was a solution to this problem ever found?
I get this problem nearly every time I flash a ROM, and the way that I fix it is to unzip the ROM, find the "broken" jar file and re-upload it to the phone using adb as per this post by firerat:
Code:
forum.cyanogenmod.com/topic/2132-need-serious-help-cant-flash-any-cm-build-but-cm-6-nightly-tests/page__view__findpost__p__21040
I hope this helps...
Well, hello guys i bought a Motorola Milestone from a friend yesterday.
And I'm that annoying kid that will probably step on your lawn again and again, but i apologize in advance for my stupid questions that will probably come after this.
But i have been at it for about 6-7 hours googling bouncing around to you youtube.
I was up halfway through the night yesterday to find a way to flash my phone with Cyna cyanogenmod.com
And through tutorials wiki.cyanogenmod.com/wiki/Motorola_Droid:_Full_Update_Guide
When i get to step:
9. Once it is selected, hit Start and wait for it to finish flashing the device.
10/28/11 12:18:51 New Log Started For Software Download.
10/28/11 12:18:55 00000de0 Phone.cpp 450 0 ERROR Generic failure when sending command.
10/28/11 12:18:55 00000de0 Phone.cpp 1556 0 ERROR GetPhoneID failed: ERROR.
10/28/11 12:19:01 The FlashLog key is turned off.
10/28/11 12:19:02 Multi upgrade started for 1 phones
10/28/11 12:19:02 [Device ID: 0] Flashing phone.
10/28/11 12:19:02 ERROR: Phone[0000]: Phone is not compatible with multi-interface super-file. - on device ID 0.
10/28/11 12:19:02 ERROR: Flash failure: Phone[0000]: Phone is not compatible with multi-interface super-file. (Error Code: 3b),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=No Codegroup - on device ID 0.
10/28/11 12:19:02 [Device ID: 0] Phone[0000]: Phone is not compatible with multi-interface super-file.
10/28/11 12:19:03 Multi upgrade finished.
I get this error through searching someone said it was a bug place the *.sbf file in C:\, My documents i tried that same error.
I tried different versions of RSD lite i tried patching the pst_flash.ini file.
After i got shutdown here i tried to push a recovery image through my computer using recovery.img.
adb shell
adb flash_image bla bla bla
i get the error access denied.
Is there any ****ing way to give my telephone a custom rom or change my default Androd bootloader recovery for rom managers?
After a while i found this, i tho to myself was the bootloader locked the whole ****ing time?
ausdroid.net/2011/06/14/an-update-on-motorolas-locked-boot-loader-situation/
ausdroid.net/2011/04/27/confirmation-motorola-to-unlock-bootloaders-for-future-android-devices
If some kind soul out there could spread some light on my issues i will be in your debt forever.
P.S sorry for all the f*cks D.S
The Droid and Milestone are very similar, but have important differences. The Milestone has a locked bootloader, while the Droid doesn't. When it comes to rooting the Milestone and installing a custom ROM, steer clear of instructions for the Droid. It'll get you nowhere.
http://www.droid-developers.org/wiki/CyanogenMod_4_Milestone_FAQ
http://android.doshaska.net/cm7
Ok, so I'll be the first to admit, I'm a bit new to all this.... I figured I was following directions, but something went amiss...
I was working through the process to put CM11 on my Razr i (which had the soak of 4.4.2 from Motorola on it...).
I unlocked the bootloader, rooted it, (but of course never made a back-up). I was able to put in TWRP into the recovery partition and attempt to flash the OS zip image - which failed.
In that thread, there were many options to try, which I did, and eventually my phone will either get stuck at the "Warning - Bootloader Unlocked" screen, or if I reboot with Power/VolDown I can get into Fastboot. But every option in Fastboot menu just reboots the phone.
I can get to the phone with Fastboot from the PC through USB - and it *looks* like I can re-flash different recovery images, but nothing seems to change. The Lebobo flasher will not flash to the device at all - keeps saying "waiting for device" with any option. I have the Motorola USB drivers loaded.
Not sure what else to try.....
Check your drivers again and even reinstall them. U will need the Motorola ones and maybe even the Google ones.
The lebobo flasher uses the 'fastboot' executable to interact with the phone in fastboot. Get a copy off the fastboot exe from the Index thread in the general section. If u have the fastboot.exe or 'fastboot' binary if u are on linux then reboot your phone in bootloader mode. Open a commandprompt in the directory where u have the fastboot executable (shift+right mouse button). Now do the command "fastboot devices" if your device shows up in it the drivers are correctly installed. If it doesn't it not. If it does, install a recovery by using the command "fastboot flash recovery recovery.img" assuming u renamed the recovery image to recovery.img.
i have the same probleme , my motorola razr i is stuck on warning ......... help me pleas:crying:
Verified Moto driver installed (reinstalled).
fastboot.exe is latest from Android SDK - api 21 version
fastboot devices shows "TA237059P0 fastboot"
fastboot flash recovery recovery.img looks like it works. on the PC says "OKAY" and finished. On the phone says Downloading.... then Flashing recovery ... but just sits there. Tried with 2 different Recovery images.
Forgot to mention - in command window on PC, when I use above commend - first thing that comes back "(bootloader) Variable not supported!"
If I use fastboot menu on the phone to then go to Recovery, the phone reboots and sits at the Warning screen again.
Lelobo still says "waiting for device" even though command line fastboot seems to connect to the device.
Wipe cache through fastboot and try again. It van help
fastboot -w give the following....
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
erasing 'userdata'...
(bootloader) Creating EXT4 FileSystem for userdata
OKAY [ 13.707s]
erasing 'cache'...
(bootloader) Creating EXT4 FileSystem for cache
OKAY [ 2.902s]
finished. total time: 16.614s
Then flashing recovery behaves same as above, except when I select it in the Fastboot menu, the phone just shuts off now (tried different recovery, now it reboots, stuck at Warning)
ccallana said:
fastboot -w give the following....
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
erasing 'userdata'...
(bootloader) Creating EXT4 FileSystem for userdata
OKAY [ 13.707s]
erasing 'cache'...
(bootloader) Creating EXT4 FileSystem for cache
OKAY [ 2.902s]
finished. total time: 16.614s
Then flashing recovery behaves same as above, except when I select it in the Fastboot menu, the phone just shuts off now (tried different recovery, now it reboots, stuck at Warning)
Click to expand...
Click to collapse
Success!! used "fastboot erase cache" instead.... then flashed in the suggested Newbie recovery on page 1 of the CM11 thread. adb wouldn't sideload the modded image, so I stuck it on an sd card and loaded it from there... and voila, it is booting!
I am trying to install lineageos for 2 days now twrp keeps giving error would anyone could send me hak86's twrp image I couldnt find on telegram sourceforge and github thanks and it is now stuck on formatting data
there is (now) a functioning link in the "main" topic forum:
see https://forum.xda-developers.com/t/...for-huawei-p-smart-2018.3980019/post-84237985
@haky 86 : thnx for that
Bokkahontas said:
there is (now) a functioning link in the "main" topic forum:
see https://forum.xda-developers.com/t/...for-huawei-p-smart-2018.3980019/post-84237985
@haky 86 : thnx for that
Click to expand...
Click to collapse
I can remake it, but I need some testers as I don't have the device right now.
@haky 86 : that would be nice, since installing the twrp failed:
$ fastboot flash recovery twrp-3.4.0.0-v1-figo-haky86.img
> Sending 'recovery' (10734 KB) OKAY [ 0.382s]
> Writing 'recovery' FAILED (remote: 'partition length get error')
> fastboot: error: Command failed
device is properly connected, I also doublechecked that bootloader is still unlocked after upgrade from emui 8 to 9.1 (Build is 9.1.0.216(C432E22R1P5))
Can we merge this topic with the following, so there is no parallel discussion in two different topics within the forum?! ;-)
=> https://forum.xda-developers.com/t/...for-huawei-p-smart-2018.3980019/post-84237985
switch recovery with recovery_ramdisk
twrp installation succeded with _ramdisk, thanks for the fast reply!
I followed then instructions from official lineage 16 wiki (https://wiki.lineageos.org/devices/figo/install) to install lineageOS 16. Sideload of the actual zip (lineage-16.0-20210115-nightly-figo-signed) in twrp also worked perfectly and I eagerly tipped on "reboot" in twrp hoping to see my new OS booting for the the first time... BUT:
Unfortunately I got stuck at a probably similar point as Capybar (see https://forum.xda-developers.com/t/...k-recovery-and-cant-boot-into-system.4126357/):
Phone stopped being able to enter any recovery at all. The system itself does not boot. The HUawei start screen "Your device has been unlocked and cannot be trustet (...) only tells me (...) "Your device is booting now...", the recovery option never appears (previously in the start screen with 'unlocked device' warning it used to suggest pressing volume UP to enter recovery, now it only shows "Your device is booting now").
Then it shows me the Teamwin Logo and at that point freezes.
I cannot acces the phone with adb oder fastboot from host machine..
=> Does anybody knows if there is a possibility to gain acces to recovery?
if stuck on Huawei splash screen, just run factory reset with stock recovery.
to boot into recovery on this crap;
* Keep pressing on vol up + vol down + power.
* Leave vol down button only and keep pressing other 2 buttons once huawei splash screen appears .
* you should able to boot into recovery.
thnx again haky !!!
Nevertheless feeling stupid now (or rather like my mum when I first modified our home-PC autoexec.bat on a 386DX machine in MS DOS to make the PC wish her a good morning on the VGA display) .Back to topic:
I managed to get the the phone start in recovery boot mode asking me
(1) Press Power key to continue
(2) Press Volume Uo key (...) to enter erecovery to restore aour device
(3) Vour device will continue to booot (...)
=> all options result in the same(?) everlasting bootloop
so I succesfully tried fastboot boot mode (error 64 message on screen) and flashed your stock recovery:
$ fastboot devices -l
> XEDDU*********** fastboot usb:2-2
$ fastboot flash recovery_ramdisk 9.1_stock_rec.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.156s]
writing 'recovery_ramdisk'...
OKAY [ 0.269s]
finished. total time: 1.425s
Rebooting phone again leads to bootloop
Edit: Not the very same bootloop since twrp-logo does not appear anymore but phone message is "Your device is booting now ... " and that's it
Got some ideas?
Edit#2 [SOLVED]: put fastboot option -w into command for flashing stock recovery => phone resurrected to stock software (at least)
Thanks for the update!
Im was stuck in the same situation. If you succeed in flashing LineageOS I would love to hear how.
Good luck!
without a phone I can't do a sh*t, try this recovery (3.5.0) and tell me if boots or not.
haky 86 said:
without a phone I can't do a sh*t, try this recovery (3.5.0) and tell me if boots or not.
Click to expand...
Click to collapse
While flashing it I get the following log:
.\fastboot flash recovery_ramdisk .\recovery.img -w
target reported max download size of 471859200 bytes
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
sending 'recovery_ramdisk' (13452 KB)...
OKAY [ 0.376s]
writing 'recovery_ramdisk'...
OKAY [ 0.102s]
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.068s]
finished. total time: 0.546s
I can boot into the recovery. My issue is, when I use wipe -> format data, it formats, says "done", but dosn't give me an option to proceed or go back. So I'm stuck there. After a hard reset I tried to boot into recovery again, but it gets stuck on the teamwin screen.
After flashing it again with the -w option, it works again.
An other issue I have is, when I try to wipe eg. cache, it works, but while trying to update the partition details, it "failed to mount '/data' (Invalid argument)". The same happens, when I install something.
Zet24 said:
While flashing it I get the following log:
.\fastboot flash recovery_ramdisk .\recovery.img -w
target reported max download size of 471859200 bytes
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
sending 'recovery_ramdisk' (13452 KB)...
OKAY [ 0.376s]
writing 'recovery_ramdisk'...
OKAY [ 0.102s]
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.068s]
finished. total time: 0.546s
I can boot into the recovery. My issue is, when I use wipe -> format data, it formats, says "done", but dosn't give me an option to proceed or go back. So I'm stuck there. After a hard reset I tried to boot into recovery again, but it gets stuck on the teamwin screen.
After flashing it again with the -w option, it works again.
An other issue I have is, when I try to wipe eg. cache, it works, but while trying to update the partition details, it "failed to mount '/data' (Invalid argument)". The same happens, when I install something.
[/QUOT]
can you pm me a screenshot?
Click to expand...
Click to collapse
1) @haky 86 : I can also boot into the (3.5.0) recovery
EDIT (fyi): could boot into that recovery, but after installation of stock rom (and likewise in official linage rom) my SIM Card was not detected.
Using "old" stock recovery [9.1_stock_rec.img] and SIM Card works fine. Still that Wifi-Password-Problem...
Zet24 said:
(...)
My issue is, when I use wipe -> format data, it formats, says "done", but dosn't give me an option to proceed or go back. So I'm stuck there. After a hard reset I tried to boot into recovery again, but it gets stuck on the teamwin screen.
(...)
Click to expand...
Click to collapse
2) @Zet24 : this looks rather to a twrp 3.4.0.0 error (?) because previously I got the same which finally ended in stucked teamwin screen and bootloop (see above)
3) @Zet24 : I managed to flash and boot into official figo lineage 16 ROM (lineage-16.0-20210122-nightly-figo-signed) by copying the zip file on sd card and install it directly in twrp (install >> from zip file) -- actually I don't know why sideload method doesn't work..
Unfortunately I couldn't not connect to wifi (see discussion in main topic Forum: https://forum.xda-developers.com/t/...for-huawei-p-smart-2018.3975303/post-83896865) even after wiping data and cache with stock recovery, but that is for another time/topic
I posted a tutorial on how to flash Lineage OS on this phone on the other Thread... the Lineage OS thread.
Bokkahontas said:
twrp installation succeded with _ramdisk, thanks for the fast reply!
I followed then instructions from official lineage 16 wiki (https://wiki.lineageos.org/devices/figo/install) to install lineageOS 16. Sideload of the actual zip (lineage-16.0-20210115-nightly-figo-signed) in twrp also worked perfectly and I eagerly tipped on "reboot" in twrp hoping to see my new OS booting for the the first time... BUT:
Unfortunately I got stuck at a probably similar point as Capybar (see https://forum.xda-developers.com/t/...k-recovery-and-cant-boot-into-system.4126357/):
Phone stopped being able to enter any recovery at all. The system itself does not boot. The HUawei start screen "Your device has been unlocked and cannot be trustet (...) only tells me (...) "Your device is booting now...", the recovery option never appears (previously in the start screen with 'unlocked device' warning it used to suggest pressing volume UP to enter recovery, now it only shows "Your device is booting now").
Then it shows me the Teamwin Logo and at that point freezes.
I cannot acces the phone with adb oder fastboot from host machine..
=> Does anybody knows if there is a possibility to gain acces to recovery?
Click to expand...
Click to collapse
Hi, How did you manage to unlock bootloader?
I f****d up.
Hi everyone. I may have bitten more than I can chew. I'm trying to install a custom ROM to my recently unlocked Redmi Note 10 Pro. It's crDroid in case that's necessary.
I did a lot of things but I forgot most of them. Here's what I remember doing:
Connected my phone to my Linux computer.
Go into fastboot modevia the following command:
Code:
adb reboot bootloader
Use TWRP by running this in a terminal:
Code:
fastboot boot twrp.img
Went in to the wipe option in TWRP and do a complete factory reset and format data.
Pushed the custom ROM file to /sdcard.
Attempted to install the zip file via TWRP.
Got an error code. Forgot the code and I didn't take note of it. (Please make fun of me).
Attempted to reboot TWRP recovery by going to Reboot > Recovery
Reached stock MIUI Recovery.
And here I am.
I can only access MIUI Recovery 5.0 and fastboot mode, both by pressing the right buttons on the device.
I don't know what a bricked device is, but it sure does feel like my device is one.
Is there a way to solve this?
zepolyerf said:
I f****d up.
Hi everyone. I may have bitten more than I can chew. I'm trying to install a custom ROM to my recently unlocked Redmi Note 10 Pro. It's crDroid in case that's necessary.
I did a lot of things but I forgot most of them. Here's what I remember doing:
Connected my phone to my Linux computer.
Go into fastboot modevia the following command:
Code:
adb reboot bootloader
Use TWRP by running this in a terminal:
Code:
fastboot boot twrp.img
Went in to the wipe option in TWRP and do a complete factory reset and format data.
Pushed the custom ROM file to /sdcard.
Attempted to install the zip file via TWRP.
Got an error code. Forgot the code and I didn't take note of it. (Please make fun of me).
Attempted to reboot TWRP recovery by going to Reboot > Recovery
Reached stock MIUI Recovery.
And here I am.
I can only access MIUI Recovery 5.0 and fastboot mode, both by pressing the right buttons on the device.
I don't know what a bricked device is, but it sure does feel like my device is one.
Is there a way to solve this?
Click to expand...
Click to collapse
Drivers installed?
Hi! How can I check if drivers are installed? I'm on Linux, if that matters.
Your device isn't bricked until you can do absolutely nothing with it. Start by reflashing the factory firmware; this should get your device running again.
You should also still be able to boot TWRP just like you did. What ROM were you trying to use?
V0latyle said:
Your device isn't bricked until you can do absolutely nothing with it. Start by reflashing the factory firmware; this should get your device running again.
You should also still be able to boot TWRP just like you did. What ROM were you trying to use?
Click to expand...
Click to collapse
That's good to hear.
I'm trying to make another attempt to boot to TWRP. I'm currently in fastboot mode: running fastboot -l devices shows this:
Code:
f8b471a6 fastboot
usb:1-5
I tried to following official TWRP instructions to flash it. Ran fastboot flash recovery twrp.img and all I get is <waiting for device> as a response after running the command in the terminal.
I unplug the cable, then plug it back in to the computer, then this is what I got:
Code:
Sending 'recovery' (131072 KB) FAILED (Write to device failed (Device or resource busy))
fastboot: error: Command failed
Any ideas on how to get around this?
zepolyerf said:
That's good to hear.
I'm trying to make another attempt to boot to TWRP. I'm currently in fastboot mode: running fastboot -l devices shows this:
Code:
f8b471a6 fastboot
usb:1-5
I tried to following official TWRP instructions to flash it. Ran fastboot flash recovery twrp.img and all I get is <waiting for device> as a response after running the command in the terminal.
I unplug the cable, then plug it back in to the computer, then this is what I got:
Code:
Sending 'recovery' (131072 KB) FAILED (Write to device failed (Device or resource busy))
fastboot: error: Command failed
Any ideas on how to get around this?
Click to expand...
Click to collapse
Your device might not have a recovery partition; in A/B partition layout devices, recovery lives in the boot image.
A bit of an explanation:
When you use fastboot boot <image> you're telling the device to load the image you're sending - so if you use fastboot boot twrp.img you're telling it to load the TWRP.img on your computer. This is what you should be using if you want to boot TWRP.
When you use fastboot flash <partition> <image> you're telling bootloader to flash the specified partition with the specified image. So, if you used fastboot flash boot twrp.img, bootloader will overwrite /boot with the TWRP image...meaning the device will only boot into TWRP.
As for why the device would only boot into stock recovery after you flashed the custom ROM, I suspect that it didn't flash the kernel, or otherwise may have corrupted the boot image. So, when the device tries to start the kernel, it failed and just boots into recovery instead.
What should I do at this point if I can't do fasboot boot <image> or fastboot flash <parition> <image> because of the <waiting for device> thing I get everytime I run those commands?
zepolyerf said:
What should I do at this point if I can't do fasboot boot <image> or fastboot flash <parition> <image> because of the <waiting for device> thing I get everytime I run those commands?
Click to expand...
Click to collapse
Reboot to bootloader. If you're currently in recovery mode, cancel the command (Ctrl+C) and use adb reboot bootloader. If you're currently in bootloader but it's not responding, just use the button combo to force a reset.
Remember, you can only use fastboot commands in bootloader mode. If you're in recovery, you can only use some ADB commands, but in this case, I don't think that will be much help.
This is just soft brick. A hard brick means no life in the device as well. In your case, you can still access recovery and fastboot. You can either use MiFlash and use fastboot to flash the stock rom (your choice if you want to relock the bootloader or not) or flash miui recovery rom directly in the custom recovery.
If I remember correctly too, crDroid requires it's provided recovery instead of TWRP so maybe that's why the installation failed.
I went into fastboot mode by pressing Vol Down + Power buttons.
Plugged the phone in to my Linux machine. Have VirtualBox recognize my device.
Opened MiFlash tool. Selected the flash rom from Xiaomi's site. Got an Antirollback error. Here's the logs:
Code:
[4:41:24 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:41:25 AM]:GetScriptDevices
[4:41:28 AM]:add device f8b471a6 index 0
[4:41:48 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:41:48 AM]:GetScriptDevices
[4:41:51 AM]:FlashingDevice.flashDeviceList.Remove f8b471a6
[4:41:51 AM]:add device f8b471a6 index 0
[4:41:51 AM]:Thread start,thread id 11,thread name f8b471a6
[4:41:51 AM]:start process id 4212 name cmd
[4:49:16 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:49:16 AM]:GetScriptDevices
[4:49:16 AM]:add device f8b471a6 index 1
[4:49:24 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:49:24 AM]:GetScriptDevices
[4:49:24 AM]:FlashingDevice.flashDeviceList.Remove f8b471a6
[4:49:24 AM]:add device f8b471a6 index 1
[4:49:24 AM]:Thread start,thread id 12,thread name f8b471a6
[4:49:24 AM]:start process id 1704 name cmd
[4:49:25 AM]:Thread stopped, thread id 12, thread name f8b471a6
[4:51:22 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:51:23 AM]:GetScriptDevices
[4:51:23 AM]:FlashingDevice.flashDeviceList.Remove f8b471a6
[4:51:23 AM]:add device f8b471a6 index 1
[4:51:23 AM]:Thread start,thread id 19,thread name f8b471a6
[4:51:23 AM]:start process id 3400 name cmd
[4:52:26 AM]:GetUserInfo
[4:52:39 AM]:authentication edl error:Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
[4:56:31 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[4:56:31 AM]:GetScriptDevices
[6:00:17 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:18 AM]:driver oem5.inf exists,uninstall,reuslt True,GetLastWin32Error
[6:00:19 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Google\Driver\android_winusb.inf to C:\Windows\INF\oem5.inf,result True,GetLastWin32Error
[6:00:19 AM]:set RegistryKey value:android_winusb.inf--oem5.inf
[6:00:19 AM]:mkdir "C:\Users\IEUser\.android"
[6:00:19 AM]:output:A subdirectory or file C:\Users\IEUser\.android already exists.
[6:00:19 AM]: echo 0x2717 >>"C:\Users\IEUser\.android\adb_usb.ini"
[6:00:19 AM]:output:
[6:00:19 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:19 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Nvidia\Driver\NvidiaUsb.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[6:00:19 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:20 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Microsoft\Driver\tetherxp.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[6:00:20 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:21 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Microsoft\Driver\wpdmtphw.inf to ,result False,GetLastWin32Error Unknown error (0xe000022f)
[6:00:21 AM]:open RegistryKey Software\XiaoMi\MiFlash\
[6:00:21 AM]:driver oem6.inf exists,uninstall,reuslt True,GetLastWin32Error
[6:00:22 AM]:install driver C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\Driver\qcser.inf to C:\Windows\INF\oem6.inf,result True,GetLastWin32Error
[6:00:22 AM]:set RegistryKey value:qcser.inf--oem6.inf
[6:01:33 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[6:01:34 AM]:GetScriptDevices
[6:01:34 AM]:add device f8b471a6 index 1
[6:01:55 AM]:lsusb path:"C:\Users\IEUser\Downloads\MiFlash\MiFlash2020-3-14-0\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
[6:01:55 AM]:GetScriptDevices
[6:01:55 AM]:FlashingDevice.flashDeviceList.Remove f8b471a6
[6:01:55 AM]:add device f8b471a6 index 1
[6:01:55 AM]:Thread start,thread id 12,thread name f8b471a6
[6:01:55 AM]:start process id 6280 name cmd
[6:01:56 AM]:Thread stopped, thread id 12, thread name f8b471a6
Any idea on what to do next?
BigChungus321 said:
This is just soft brick. A hard brick means no life in the device as well. In your case, you can still access recovery and fastboot. You can either use MiFlash and use fastboot to flash the stock rom (your choice if you want to relock the bootloader or not) or flash miui recovery rom directly in the custom recovery.
If I remember correctly too, crDroid requires it's provided recovery instead of TWRP so maybe that's why the installation failed.
Click to expand...
Click to collapse
It might as well be a brick haha. I must be dumb (very likely) or there's just not a lot of clear and comprehensive resources out there to fix this kind of thing.
Ahh anti roll back error is pretty simple to fix, you just have to remove the check from the .bat files, there are tutorials on YT that can help, after that reflash stock rom in MiFlash.
If you're worried about anti roll back, don't worry, ARB value for the device has been 3 so far so it's safe to downgrade. Goodluck
Seeing a ton of Bricked Notes on here this last week, Y`all making me nervous about doing anything with mine lol
I faced this problem in linux got around it with usb 2.0 interface doesn't worked with usb 3.0 and above but my device was different when I got this recovery flash waiting problem. Also try to updated the platform tools.
So the solution was to entirely ditch Linux and use Windows to play with fastboot and adb commands via the terminal.
I don't understand why it worked when I did it on Windows when I was using the same platform tools on Linux. Oh well.