My Nexus One is stuck on boot screen and keeps recycling/vibrating. To condense information, here are bullet points of the situation:
-Nexus One 2.3.6 with unlocked bootloader
- PASSIMG.IMG is wrong or missing in HBOOT
-Can't access the sd root because I lost my sd adapter
-I've tried to fastboot recovery-RA-v2.2.1.img and Clockorange but I think that because I don't have the SU files in a folder titled SU on my sd, it doesn't go into the recovery menu
-When I cmd fastboot devices the serial comes up, but when I cmd adb devices, nothing comes up
-Can't access sd storage to move the SU folder via cmd
I've been working on this the past two days and searching and trying anything and everything. And nothing has worked. Any help would be great.
You don't need anything on your sdcard (or your sdcard itself for that matter) to put a custom recovery on your phone. Try this after putting your phone into fastboot mode and getting your cmd prompt up on the computer:
Code:
fastboot flash recovery "c:\location\to\recovery.img"
fastboot boot recovery "c:\location\to\recovery.img"
From here, try a factory reset.
And adb won't be able to see your phone until you are either in recovery or fully booted up in Android (only with USB Debugging enabled).
When I do "fastboot boot recovery recovery-RA-v2.2.1.img" it comes up cannot load recovery.
Any ideas?
And once that goes through, do I boot through recovery on the phone or through command prompt?
Thank you for the reply.
Is the recovery in the folder where you are typing the command? And have you verified that the md5 sum of the recovery is correct?
And, I always just change the command from flash to boot to boot into the recovery the first time. Otherwise, if you are running a stock Android version, your recovery might get restored back to the stock recovery (Android has checks in place for that).
Nevermind, I did get it to go through, but then my N1 reboots on its own and is still stuck at the bootscreen
Ok, do you want to continue running stock, or would you like to try a custom ROM? Because, it sounds like you will need to reload your ROM (assuming the Factory Reset/Data Wipe didn't work). They have a couple of rooted extremely close to stock versions on here, or you might want to give CM7 or MIUI a shot. I would also go and get temasek's system-only format since Amon_RA doesn't give you the option to format your /system partition. You can find the file in his mediafire folder http://mediafire.com/temasek
My original intentions were to put CM7 on my phone because Gingerbread began to crash a lot. So in that case, how am I supposed to install the CM7 ROM onto my phone if I can't get past the bootscreen?
So, the fastboot boot command doesn't work?
fastboot does work, adb doesn't
No, does the
Code:
fastboot boot recovery "c:\location\to\recovery.img"
get you into recovery? Or does it still freeze on the X screen (when you say bootscreen, I assume you mean the X)?
Sounds like the recovery isn't installing with fastboot? Do you get any error messages?
It will still freeze at the X and never boots into recovery.
seb0 said:
It will still freeze at the X and never boots into recovery.
Click to expand...
Click to collapse
I got exactly the same problem as you. Didn't you see my post?
Btw, the fastboot boot recovery "c:\location\to\recovery.img" command doesn't work, whoever gave that tips.
I got an idea, but not sure about it:
Get someone who has a working Nexus One to make an nandroid backup, and send the boot.img and system.img and fastboot it into our devices?
mrBira said:
Btw, the fastboot boot recovery "c:\location\to\recovery.img" command doesn't work, whoever gave that tips.
Click to expand...
Click to collapse
What do you mean it doesn't work? I know it works because I've used it many times. Does it give an error? Are you actually changing the c:\location\to\recovery.img to the proper location and name of the recovery file?
bassmadrigal said:
What do you mean it doesn't work? I know it works because I've used it many times. Does it give an error? Are you actually changing the c:\location\to\recovery.img to the proper location and name of the recovery file?
Click to expand...
Click to collapse
Yes ofc i got the path right. It gives this error:
"cannot load 'recovery'"
mrBira said:
Yes ofc i got the path right. It gives this error:
"cannot load 'recovery'"
Click to expand...
Click to collapse
That typically means that it can't find the file (which seems like it is looking for just recovery, not recovery.img or whatever the name is). Have you tried using tab completion to make sure it is the right filename?
bassmadrigal said:
That typically means that it can't find the file (which seems like it is looking for just recovery, not recovery.img or whatever the name is). Have you tried using tab completion to make sure it is the right filename?
Click to expand...
Click to collapse
If i write wrong filename it gives me another error. Yes the filename and path is 100% accurate.
I'm trying to fastboot flash system system.img to then fastboot boot boot.img to my N1 but everytime I flash the system.img it gets stuck a 1/4 of the way.
So basically, can someone please tell me how to get my N1 to stock so I can start from scratch with the CM7 flash?
Here is my system info:
-Nexus One (Unlocked) - T-Mobile service provider
-Android Version- 2.3.6
-Baseband Version- 32.41.00.32U_5.08.00.04
-Kernel Version- 2.6.35.7-59465-g42bad32 [email protected] #1
-Build Number- GRK39F
I have fastboot access but no adb access.
If you can provide the necessary files needed for this I would greatly appreciate it.
mrBira said:
If i write wrong filename it gives me another error. Yes the filename and path is 100% accurate.
Click to expand...
Click to collapse
Have you tried any additional recoveries? It has been awhile since I used that command, but I know it has worked in the past.
seb0 said:
I'm trying to fastboot flash system system.img to then fastboot boot boot.img to my N1 but everytime I flash the system.img it gets stuck a 1/4 of the way.
So basically, can someone please tell me how to get my N1 to stock so I can start from scratch with the CM7 flash?
Here is my system info:
-Nexus One (Unlocked) - T-Mobile service provider
-Android Version- 2.3.6
-Baseband Version- 32.41.00.32U_5.08.00.04
-Kernel Version- 2.6.35.7-59465-g42bad32 [email protected] #1
-Build Number- GRK39F
I have fastboot access but no adb access.
If you can provide the necessary files needed for this I would greatly appreciate it.
Click to expand...
Click to collapse
You won't have adb access unless you are in recovery or booted into Android with USB Debugging enabled.
Where did you get the system.img and boot.img files from?
http://forum.xda-developers.com/showthread.php?t=1061648
This was the only system.img and boot.img file I could find.
Related
Hello all.... I am working on a group project where we will be using a dev G1. The phone was shipped to a another group member and before I can get my hands on it, he decided to upgrade the firmware from 1.0 to 1.6, having very little knowledge of android beforehand and therefore he cant really tell me what exactly he did either. He followed the directions on the HTC website. As far as i can tell, I do have the 26I radio, engineering SPL and 1.6 installed currently, not sure about the recovery though (i.e. stock 1.0 or 1.6). When I got the phone, root access was gone but followed some simple steps on this website to regain it. By way of typing in "su" in terminal emulator and in ADB shell, I now also have su. However I still cant flash anything. When trying to flash cm 4.2.5 in the recovery, the system verifies it and then aborts installation. I then tried to install the Amon-RA recovery to no avail. Tried fastboot, ADP, terminal, im not sure how to access the /data/ partition on the phone and there is no option for acessing the console in the recovery menu. Installing through ADB dosnt work, no test-keys in current recovery. In fastboot it says "okay" for both sending and writing the recovery but rebooting into recovery shows that it didnt work. In terminal it says "flash_image: not found". I'm kinda lost and need some help....
All I need is cm4.2.5 on the phone with root.
Thanks in advance.....
Edit: I triple and quadruple checked the name of the recovery image when trying to install through terminal. I'm pretty sure it cant find the command "flash_image" and not the file itself. Just wanted to clarify...
You could try downgrading to RC29: http://wiki.cyanogenmod.com/index.p...ngrading_to_RC29_.28US.29_or_RC7_.28Europe.29
halr9000 said:
You could try downgrading to RC29: http://wiki.cyanogenmod.com/index.p...ngrading_to_RC29_.28US.29_or_RC7_.28Europe.29
Click to expand...
Click to collapse
Tried that, already... That method only works for the stock T-Mobile G1's which have a different SPL. The Dev G1's come with engineering SPL and I have no idea how to flash the .nbh image from that. All it does I think is enable Fastboot, I cant get it to do anything else.
This fails?
fastboot flash recovery recovery.img
Nope... No luck, it says:
sending 'recovery' <4456kb>.... OKAY
writing 'recovery' <4456kb>.... OKAY
and then I reboot using "fastboot reboot", wait till the homescreen loads, and then go back into recovery and it still shoes the the triangle and the !.....
Bump...
Anyone?? Right now we just have a reallly expensive paper-weight in our hands ANY help/thoughts/comments would be very appreciated...
This thread is meaningless since there is NO SUCH THING as a "DEV G1".
alilbitanuthin said:
Hello all.... I am working on a group project where we will be using a dev G1. The phone was shipped to a another group member and before I can get my hands on it, he decided to upgrade the firmware from 1.0 to 1.6, having very little knowledge of android beforehand and therefore he cant really tell me what exactly he did either. He followed the directions on the HTC website. As far as i can tell, I do have the 26I radio, engineering SPL and 1.6 installed currently, not sure about the recovery though (i.e. stock 1.0 or 1.6). When I got the phone, root access was gone but followed some simple steps on this website to regain it. By way of typing in "su" in terminal emulator and in ADB shell, I now also have su. However I still cant flash anything. When trying to flash cm 4.2.5 in the recovery, the system verifies it and then aborts installation. I then tried to install the Amon-RA recovery to no avail. Tried fastboot, ADP, terminal, im not sure how to access the /data/ partition on the phone and there is no option for acessing the console in the recovery menu. Installing through ADB dosnt work, no test-keys in current recovery. In fastboot it says "okay" for both sending and writing the recovery but rebooting into recovery shows that it didnt work. In terminal it says "flash_image: not found". I'm kinda lost and need some help....
All I need is cm4.2.5 on the phone with root.
Thanks in advance.....
Edit: I triple and quadruple checked the name of the recovery image when trying to install through terminal. I'm pretty sure it cant find the command "flash_image" and not the file itself. Just wanted to clarify...
Click to expand...
Click to collapse
Pretty sure there is...
http://developer.htc.com/adp.html
Bump...
anyone?
alilbitanuthin said:
Pretty sure there is...
http://developer.htc.com/adp.html
Click to expand...
Click to collapse
Do you see ANYTHING on there that says "G1"?
Answer: No you definitely do NOT.
If I remember correctly, after you use fastboot to flash the new recovery image, you can't let the phone reboot or it will overwrite the recovery with the stock recovery image
The solution would be to use fastboot to flash either Cyanogen's or Amon_RA's recovery image, and be quick here, but when you send the fastboot reboot command be holding down the home button on the phone so it will boot to the custom recovery image
lbcoder said:
Do you see ANYTHING on there that says "G1"?
Answer: No you definitely do NOT.
Click to expand...
Click to collapse
lol, no need to nitpick, about the name no less. Thats the least of my worries
As long as you get the message across...
jackslim said:
If I remember correctly, after you use fastboot to flash the new recovery image, you can't let the phone reboot or it will overwrite the recovery with the stock recovery image
The solution would be to use fastboot to flash either Cyanogen's or Amon_RA's recovery image, and be quick here, but when you send the fastboot reboot command be holding down the home button on the phone so it will boot to the custom recovery image
Click to expand...
Click to collapse
That maybe it I'll give it a try as soon as I get back home. Thanks a lot for the help!!
Thanks a lot jackslim, finally got it to work!
My question is similar to 'nikpmr's troubles but different enough I think they deserve a separate post.
The Problem as UnderstoodI was trying to root my device following the guide at this website. It's so simple it's a wonder I messed up. I think my failure was that I thought the drivers installed when I connected the phone were enough so I skipped that step. Then when running fastboot flash recovery.img the install failed. So I saw on some forum that it was supposed to be fastboot flash boot recovery.img of course now I know if anything it ought to have been "recovery" not "boot".
What I've Tried & Partial SolutionAt first I was just stuck in a boot loop and selecting "sideload" from the CWM recovery failed to allow me to connect with ADB or fastboot. i.e. Running "fastboot devices" and "adb devices" both returned as having no devices connected to my computer. So I installed the HTC Sync and promptly uninstalled the non driver parts of the app. Then I installed USBdeview and used it to uninstall all the USB devices associated with my HTC First. After doing that I learned booting into HBOOT allowed me to connect to the computer using fastboot and after then booting to the CWM Recovery I was able to connect using ADB to do a sideload. So I guess I'm about halfway there. Unfortunately after looking up the newest RUU and attempting to sideload it using "adb sideload OTA_MYST_UL_1.08.502.1-1.08.502.4.zip" the sideload failed. After selecting "- install zip from sideload" I get a message twice of "failed to open driver control: No such file or directory". It also failed when I attempted it with a similar fastboot command. So from all that I surmise my ROM is ruined and just needs to be replaced.
QuestionSo how do I go about replacing this ROM and boot partition? And, which ROM should I use? Is the one I got from the RUU site suitable? And what about the radio? I just need my phone to work. I can worry about rooting later. At this point I think I know what's happened but I don't know where to begin reading to figure out how to fix it myself.
Thanks for reading,
Relevant HBOOT text:
Code:
*** TAMPERED ***
*** UNLOCKED ***
MYSTUL PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.15.40.00.13_2
OpenDSP-v9.2.0268.1214
eMMC-boot
Mar 22 2013,21:29:50:1682
1. you had to type in fastboot flash recovery recovery.img NOT fastboot flash boot recovery.img
Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload
abrahammmmmmm_ said:
Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload
Click to expand...
Click to collapse
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.
bnjo said:
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.
Click to expand...
Click to collapse
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread
Success!
abrahammmmmmm_ said:
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread
Click to expand...
Click to collapse
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
Great! glad to hear I could help. Yes it's always nice knowing when something I've said has helped someone in any way
bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.
russian392 said:
usually after changing a kernel, it takes a while to boot cause...well you get it right?
Click to expand...
Click to collapse
Yes I get it.
russian392 said:
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.
Click to expand...
Click to collapse
That's what I thought happened. If I had stopped to read the help on fastboot before running "fastboot flash boot recovery.img" I wouldn't have made that mistake because I would have seen I wanted to flash recovery. One thing I *did not* know, which I'm glad to know, was that the boot.img contains the kernal. I was thinking Android was more similar to IBM style PCs than it is and therefore the boot.img was analogous to a bootloader like grub or lilo.
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
bnjo said:
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
in a nutshell yes, the boot.img uses the fstab
btw 10 posts you'll be "verified"
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
Yep that's correct.
The name correlation is booting up requires kernel there for kernel is called beet.IMG
Thing about custom kernels, they aren't like that and simply contain modded files and pretty much an in packaged kernel.
Sent from my HTC first using xda app-developers app
stock recovery
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted
astrit1995 said:
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted
Click to expand...
Click to collapse
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!
Serupo said:
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!
Click to expand...
Click to collapse
Thank you for your help,i solved my problem yesterday but i think im gona need this sometime...
My apologies if this has already been posted. I've been looking all morning but haven't seen anyone with the same issue.
Unlock bootloader: no problem.
Flash TWRP: I downloaded from http://teamw.in/project/twrp2/275, and I got an error about partition size mismatch, but that's ok, right?
But when I try to enter recovery, all I get is the warning screen that my phone is unlocked. The drivers are certainly installed correctly, and fastboot is working fine. I just can't get into recovery to flash a ROM!
Restoring to 4.4.4 stock worked like a charm.
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
I've re-enabled USB debugging. Do I dare try to flash a custom recovery again?
Pandae said:
Do I dare try to flash a custom recovery again?
Click to expand...
Click to collapse
You can use Flashify to make a backup of your current recovery and to flash TWRP.img. should work like a charm.
But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.
Pandae said:
But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.
Click to expand...
Click to collapse
You're right. Latest motorola driver and [TOOL]Minimal ADB and Fastboot will do the trick.
Sorry, I should have clarified that when flashing TWRP, I've already been using fastboot.exe from a command line (and administrator level), with the drivers correctly installed. That's how I was able to unlock in the first place.
I did try it with the version of Fastboot you linked to (what I have works peachy for my Nexus 7), still the same thing. I can't boot into recovery and only get stuck at the Motorola unlocked warning.
Pandae said:
I can't boot into recovery and only get stuck at the Motorola unlocked warning.
Click to expand...
Click to collapse
Oh. Sorry. Can you post the output (terminal & device) of
Code:
fastboot devices
fastboot flash recovery NAME_OF_RECOVERY.img
I'd done "fastboot devices" already to verify, and it returns the serial number, though as I said it's clearly working since I was able to unlock as well as flash recovery. I'm flashing "TWRP2801-titan-motog-2014.img" that I downloaded from the TWRP site, and fastboot gives the standard messages about size and success (and my phone gives the size mismatch error).
It's so strange to me. I've flashed a custom recovery dozens of times on both generations of my Nexus 7s, but I've never seen this.
Pandae said:
It's so strange to me.
Click to expand...
Click to collapse
Yeah......have to meditate about that problem....... is your battery low? Fastboot mode of the device gives me all sorts of problems if it detects low battery
I had been using fastboot at 100% (literally finished a full charge) and 84%, but thanks for the continued attempts at explanation.
Oh, did you check the md5 checksum of your download?
Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?
Pandae said:
Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?
Click to expand...
Click to collapse
If you are willing to risk it, try a fresh download and try again. I've flashed TWRP more than 20 times by now and never recieved an error whatsoever. It basically the easiest thing to do.
Incase you are stuck again, don't reflash the entire stock rom. Just flash the recovery.img from the stock rom files.
OR
Try this:
HOW TO ROOT MOTO G 2014 with Temporary Custom Recovery
Cheers
I've flashed a custom recovery many a time and have helped people through it, though on Nexus 7s.
Now shall I compound the mystery? I didn't think yet to use ADB to make my phone reboot to recovery. I had assumed recovery wasn't working. So here we go, after booting into Android:
adb reboot devices: my phone's there.
adb reboot recovery: TWRP's working?! And now root is complete!
It doesn't make sense to me why I can't get into recovery from the bootloader, but I can get into it with the simple ADB command. But I appreciate all the help, thanks!
Pandae said:
It doesn't make sense to me why I can't get into recovery from the bootloader
Click to expand...
Click to collapse
A little workaround:
Install Android Terminal Emulator
Add "Term shortcut" widget.
In "Arguments" enter
Code:
su -c reboot recovery
Here're the official links for Cherry Mobile One H940:
For fastboot flashable images:
Builds Available: LBY29G, LMY47O
Download: here
For OTAs:
Build: LBY29G -> LMY47O
Android Version: 5.1 (Beta) -> 5.1 Official
Download: here
Flashing Instructions:
A. Using ADB sideload (for recovery flashable update zips):
1.) Flash stock recovery.
2.) Boot to stock recovery.
3.) Perform up + power button to show menu.
4.) Select Apply update from ADB.
5.) Install ADB drivers if on Windows and not yet installed.
6.) Open cmd prompt.
7.) Change directory to where you downloaded the update zip.
8.) Issue cmd: adb sideload <update.zip filename>
9.) Wait until completed.
10.) Select reboot.
B. Using fastboot:
1.) Boot into bootloader.
2.) Flash image using fastboot flash <partition name> <image filename>.img command.
3.) Reboot using fastboot reboot command.
C. Using DD (for flashing images like system.img):
1.) Boot into custom recovery. (you could use fastboot boot custom-recovery.img so that you don't overwrite your existing one)
2.) Push image file to /sdcard using adb push command. (you might have to mount the sdcard partition before doing this)
3.) Open an ADB command shell.
4.) Go to /sdcard.
5.) Find the system partition by issuing a cat /proc/partitions command. It should be the one sized exactly 1GB (1,024,000 shown).
6.) Use dd if=/sdcard/<image filename>.img of=/dev/block/<name of partition> .
7.) Reboot either using custom recovery or just issuing an adb reboot after exiting from ADB command shell.
do you have another working file for LMY47O system.img? i'm getting a fastboot flash fail (chunk unkown) error. thanks
Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.
intersectRaven said:
Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.
Click to expand...
Click to collapse
same problem here
thank you
Uploaded. If it still fails, you might have to use dd to restore. Odd that it fails now when it was fine before. :/
OTA Flashing Error
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.
erickho0407 said:
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.
Click to expand...
Click to collapse
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.
intersectRaven said:
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.
Click to expand...
Click to collapse
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.
erickho0407 said:
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.
Click to expand...
Click to collapse
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.
intersectRaven said:
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.
Click to expand...
Click to collapse
Ok. So this means that I reflash boot.img right (would probably use fastboot). Thank you very much for assistance
Sir
can you capture ota for myphone uno
gabisonfire98 said:
Sir
can you capture ota for myphone uno
Click to expand...
Click to collapse
Unfortunately, I don't have an Uno so no.
still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM
Working internal detect for pc and file ?
marjoejoejoe said:
still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM
Click to expand...
Click to collapse
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.
intersectRaven said:
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.
Click to expand...
Click to collapse
I'll have another go at it later today. Was able to flash my own backup using CWM
marjoejoejoe said:
I'll have another go at it later today. Was able to flash my own backup using CWM
Click to expand...
Click to collapse
Still, it should be foolproof. I already checked and double-checked the system image I uploaded and it's mountable in Linux so it should restore correctly like the previous LBY image. I can't think of any other reason aside from some sort of protection that would disallow flashing of the system image through both fastboot and dd.
*On second thought, I'm reupping the image. I just flashed it using dd on my device and it works perfectly.
success, was running a windows 7 virtual machine in OSX. it must have been a protection, you are right...ran it using OSX instead (stupid me, why i didn't use it in the first place for fastboot).
files are good to go thanks man
Need help in Flashing the Stock Recovery.
Hi Guys,
I need help in flashing the stock recovery.
I've used the ALL-IN-ONE TOOL to unlock my phone's bootloader, flash the PhilZ Touch Customer recovery and Root my CM1
[http://forum.xda-developers.com/cro.../tool-master-tool-unlock-bootloader-t2997696]
However I'm unsuccessful flashing the stock recovery from the ALL-IN-ONE TOOL so I can update my phone's software to Android 5.1.1.
Can I flash the stock recovery using one of the files here? If yes, can someone please teach me how.
Thanks in advance!
OTG
Hi,
Just a quick question, after flashing using this ROM, will CM One support OTG? Or do I need to root the phone first? Is there a way to add support for OTG?
Pardon me if this may not be much related to the topic.
I have the bootloader unlocked and everything ready to go.
However, when I execute "fastboot flash recovry <recovery_file_name>.img" the first thing that pops up on the cmd is:
(bootloader) has_slot:recovery not found
(bootloader) is_logical:recovery not found
After this it continues the flashing process and finishes with the okay status
However, after rebooting using "fastboot reboot" when I go back into the bootloader and select the recovery option I end up with the droid on his back and an orange triangle with an exclamation mark over him and No Command written under him
Can anyone help with this issue? I really want to flash a new ROM onto my nexus and I also really really want TWRP to work
Thanks,
Danush
Have you tried spelling "recovery" with an "e"?
It may be that your file name isn't properly spelled. I either rename the image to "TWRP. img" or copy the file name in Explorer and paste it into the CMD window so that there is no possibility of mis-spelling.
And another thought - is the TWRP image in the same directory as the fastboot exe?
dahawthorne said:
Have you tried spelling "recovery" with an "e"?
Click to expand...
Click to collapse
Oh yeah that's just a typo in my post ?
Thanks for pointing it out.
I do spell the "recovery" with an "e" and yet I have these issues
I added more comments while you were replying.
Try this:
https://forum.xda-developers.com/showpost.php?p=73648849&postcount=6
Do you have stock Android installed? It will replace any custom recovery with the stock recovery when you boot, unless you've flashed a kernel, mod (e.g. Magisk) or similar that disables that feature.
Don't reboot the device after flashing, boot to recovery instead.
(Don't bother with those "errors", they're just telling you that your device isn't A/B or have logical partitions.)
Edit: oh yeah... Should have checked the link @dahawthorne posted before posting myself. It tells you the same thing. D'oh!
Didgeridoohan said:
Do you have stock Android installed? It will replace any custom recovery with the stock recovery when you boot, unless you've flashed a kernel, mod (e.g. Magisk) or similar that disables that feature.
Don't reboot the device after flashing, boot to recovery instead.
(Don't bother with those "errors", they're just telling you that your device isn't A/B or have logical partitions.)
Edit: oh yeah... Should have checked the link @dahawthorne posted before posting myself. It tells you the same thing. D'oh!
Click to expand...
Click to collapse
Thanks so much for all the help!! After you mentioned it, it kinda hit me that yeah maybe that is what is happening since I used to reboot the device so maybe it was replacing TWRP with the stock recovery.
Hi,
My problem with Redmi Note 4 Snapdragon 625 2,02 GHz and unlocked trying to flash TWRP is like this (phone is in fastboot mode):
PS C:\Users\Dell\Downloads\platform-tools-latest-windows\platform-tools> fastboot devices
55050ae09804 fastboot
PS C:\Users\Dell\Downloads\platform-tools-latest-windows\platform-tools> fastboot flash recovery
fastboot: error: ANDROID_PRODUCT_OUT not set
How can I solve it? Please, help!
Didgeridoohan said:
Do you have stock Android installed? It will replace any custom recovery with the stock recovery when you boot, unless you've flashed a kernel, mod (e.g. Magisk) or similar that disables that feature.
Don't reboot the device after flashing, boot to recovery instead.
(Don't bother with those "errors", they're just telling you that your device isn't A/B or have logical partitions.)
Edit: oh yeah... Should have checked the link @dahawthorne posted before posting myself. It tells you the same thing. D'oh!
Click to expand...
Click to collapse
Don't reboot after flashing? Like when i try it says img unsigned or corrupted, and when i try to then boot into recovery via "fastboot boot recovery" i get sent to the normal Android OS, so what im getting from this is that i somehow have to manually get into the "no command" error window and then power+volume up and that just works? Ill test that, would be really awesome if it does.
Oh yea and booting into the twrp image with "fastboot boot twrp.img" sends to normal os aswell btw.