I want to upgrade a US T-Mobile G1 to 2.1. Is the following procedure correct? (Don't need to backup.)
In bootloader flash RC29 DREAIMG.nbh. Reboot.
Type telnetd, install Android Telnet Client and root.
Install recovery-RA-dream-v1.7.0-cyan.img using Telnet Client.
In recovery flash G1-radio-2_22_23_02.zip. Reboot.
In recovery flash spl_1_33_2003.zip. Reboot.
In recovery flash FR-recovery-v1.5.3-CustomMTD_S.zip. Reboot.
In recovery flash signed-SuperE103.zip then flash gapps-mdpi-FRF91-3-signed.zip then flash FR-boot-v1.5.3-CustomMTD_S.zip. Reboot.
Your way will work but I recommend a minor change iif you are using the rc29 method of rooting:
In bootloader flash RC29 DREAIMG.nbh. Reboot.
Type telnetd, install Android Telnet Client and root.
Install recovery-RA-dream-v1.7.0-cyan.img using Telnet Client.
In recovery flash spl_1_33_2003.zip. Reboot. (Will return to recovery)
boot fastboot and flash the 2.x radio (info on my 1.33.2003 post.. and the *.img file is in the g1boot.zip)
while in fastboot wipe so custom mtd works 'fastboot erase system -w' and 'fastboot erase boot'
In recovery flash FR-recovery-v1.5.3-CustomMTD_S.zip. Reboot.
In recovery flash signed-SuperE103.zip then flash gapps-mdpi-FRF91-3-signed.zip then flash FR-boot-v1.5.3-CustomMTD_S.zip. Reboot.
I'm not 100% sure of that gapps package.. just check the super-e page if its correct
Edit: If you don't want to downgrade first look at:
http://forum.xda-developers.com/wiki/index.php?title=User:Ezterry/G1_1.6_To_Custom_Firmware
Thanks for the links. What is the advantage of installing radio via fastboot instead of recovery?
felix1234 said:
Thanks for the links. What is the advantage of installing radio via fastboot instead of recovery?
Click to expand...
Click to collapse
Rather than re-iterate see my post here: http://forum.cyanogenmod.com/topic/...e-via-fastboot/page__view__findpost__p__44790
In short it should be of similar difficulty for you the user and it has slightly less risk (not that there was much risk in flashing a 2.x over a 1.x one in recovery)..
For many scenarios that could brick however: if you flash via fastboot you will likely continue to be able to access fastboot after the flash; thus able to fix the phone.. while if you flash via recovery you get stuck in "boot mode 3" unable to boot anything without JTAG.
Thanks for explaining and writing the exploit guide. Will try!
Hi, can anyone clarify this instruction, I have just finished unlocking bootloader and about to install custom recovery:
Install the build of TWRP using your method of choice, but you must actually flash TWRP to recovery. No fastboot booting it. We need it in recovery so that this build of TWRP will be flashed to your boot. This new build of TWRP has features in it to easily restore your original boot.
shadow071506 said:
Hi, can anyone clarify this instruction, I have just finished unlocking bootloader and about to install custom recovery:
Install the build of TWRP using your method of choice, but you must actually flash TWRP to recovery. No fastboot booting it. We need it in recovery so that this build of TWRP will be flashed to your boot. This new build of TWRP has features in it to easily restore your original boot.
Click to expand...
Click to collapse
The statement means you have to flash(install) the custom recovery by using a command like:
Code:
fastboot flash recovery recovery.img
Or by using a toolkit, however you can't just boot the recovery with a command like this:
Code:
fastboot boot recovery.img
crushalot said:
The statement means you have to flash(install) the custom recovery by using a command like:
Code:
fastboot flash recovery recovery.img
Or by using a toolkit, however you can't just boot the recovery with a command like this:
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
thanks ..that really helped
Hi, is there a way to root through stock recovery? I'm unable to either flash recovery or boot it through
Code:
fastboot boot recovery.img
, i've tried through stock recovery but it says zip isnt signed, is there a way to sign it?
Terramoto said:
Hi, is there a way to root through stock recovery? I'm unable to either flash recovery or boot it through
Code:
fastboot boot recovery.img
, i've tried through stock recovery but it says zip isnt signed, is there a way to sign it?
Click to expand...
Click to collapse
I'm pretty sure it's not possible with stock recovery.
I also think your command might be what's messing you up...
To boot recovery wouldn't be
Code:
fastboot boot recovery recovery.img
I've never tried this so not 100% sure.
To install recovery the command would be...
Code:
fastboot flash recovery recovery.img
I dont think so, because its able to boot it just doesnt get into the recovery, its the same problem when i flash it, it boots but it doesnt load recovery. Damn it, all this bloatware here hunting my privacy and i can't remove it and one of the apps is auto turning wifi on... HTC never more.
It's not the first time I try to flash a recovery without success:
---------------------------------
fastboot flash recovery twrp.img
sending 'recovery' (10615 KB)...
(bootloader) USB download speed was 13864kB/s
OKAY [ 0.800s]
writing 'recovery'...
(bootloader) Flash of partition 'recovery' requested
FAILED (remote: Partition not found)
finished. total time: 0.814s
---------------------------------
Attached: driver loaded in fastboot mode, and drivers used when phone has booted
So, I don't think it's a problem of drivers. I'am able to flash a kernel, I can use fastboot commands (like devices, getvar, etc) ... but not to flash recovery.
I'm running a cm11 LBL with williams kernel v9.1
Any idea ??
Thanks
sambastrakan said:
It's not the first time I try to flash a recovery without success:
---------------------------------
fastboot flash recovery twrp.img
sending 'recovery' (10615 KB)...
(bootloader) USB download speed was 13864kB/s
OKAY [ 0.800s]
writing 'recovery'...
(bootloader) Flash of partition 'recovery' requested
FAILED (remote: Partition not found)
finished. total time: 0.814s
---------------------------------
Attached: driver loaded in fastboot mode, and drivers used when phone has booted
So, I don't think it's a problem of drivers. I'am able to flash a kernel, I can use fastboot commands (like devices, getvar, etc) ... but not to flash recovery.
I'm running a cm11 LBL with williams kernel v9.1
Any idea ??
Thanks
Click to expand...
Click to collapse
I am guessing the reason you are running CM11 LBL is due to the restriction imposed by a locked bootloader and not because you are choosing to miss out on all the Lollipop fun. If that's the case, I don't think you can flash a recovery via fastboot the same way you can with an UBL. You said it yourself that you have tried flashing recoveries multiple times w/o success. As far as I know, your bootloader needs to be unlocked for flashing via fastboot commands.
On the other hand if your bootloader's unlockable or you relocked it sometime in the past and forgot about it, I suppose unlocking it would do the trick. Just in case you don't know, dial up *#*#7378423#*#* and see if its unlockable.
Also what is your current recovery? I am guessing it one that came with the kernel you are using and not something you flashed separately?
Btw did you flash Williams kernel separately or did it come with the ROM? If you did flash it separately then how did you do it? Also you mentioned you flashed a kernel - did you mean via fastboot or something else like FlashTool?
No. My bootloader is unlocked (verified and I have a custom kernel running).
At the present time my recoveries are in the rom. But williams kernel is compatible with fotakernel so I should be able to flash a recovery and use it but ...
thanks
sambastrakan said:
No. My bootloader is unlocked (verified and I have a custom kernel running).
At the present time my recoveries are in the rom. But williams kernel is compatible with fotakernel so I should be able to flash a recovery and use it but ...
thanks
Click to expand...
Click to collapse
Since your bootloader's unlocked and your phone's probably rooted, why don't you use Rashr to flash the file? It will replace the recovery you have right now (cyanogenmod recovery?) with the one you wanna flash.
Note: This recovery stays even when you flash new ROMs so if want something else you will have to reflash via Rashr or flash stock firmware kernel with FlashTool.
Also if you switch to Lollipop, you can have dual recoveries if you follow the instructions on the Tangerine kernel thread.
http://forum.xda-developers.com/xperia-sp/orig-development/kernel-tangerine-kernel-v1-t3073297
Edit: What recovery do you have with Williams kernel right now?
Williams kernel.
Way back when i was using it v8 i tried flashing recovery.img from Rasht, it said recovery flashed, but nothing changed.
I did tried fastboot it also failed (can't remember what was the message in flashtool).
I think the culprit here is the kernel.
akashsaini7 said:
Williams kernel.
Way back when i was using it v8 i tried flashing recovery.img from Rasht, it said recovery flashed, but nothing changed.
I did tried fastboot it also failed (can't remember what was the message in flashtool).
I think the culprit here is the kernel.
Click to expand...
Click to collapse
It is very possible ...
Thx
Useful
There is a program called AdbDriverInstaller.exe. If you want me to send to you just P.M. me. It's actually very good in finding drivers. I used to have a problem installing CM11 in CWM and this one helped me.
kojata said:
There is a program called AdbDriverInstaller.exe. If you want me to send to you just P.M. me. It's actually very good in finding drivers. I used to have a problem installing CM11 in CWM and this one helped me.
Click to expand...
Click to collapse
thank you. i will have a look.
facing the same problem.. did u manage to fix it yet?
l2azoredge said:
facing the same problem.. did u manage to fix it yet?
Click to expand...
Click to collapse
not fixed neither understanded but there are 2 turnarounds:
1- using rashr app to flash the img
2- using command: dd if=recovery.img of=/dev/block/mmcblk0p11
if you can't enter your recovery after that the guilty is the kernel. Williams kernel is not compatible with recovery partition even if it says it is in 1st post.
sambastrakan said:
not fixed neither understanded but there are 2 turnarounds:
1- using rashr app to flash the img
2- using command: dd if=recovery.img of=/dev/block/mmcblk0p11
if you can't enter your recovery after that the guilty is the kernel. Williams kernel is not compatible with recovery partition even if it says it is in 1st post.
Click to expand...
Click to collapse
ive already tried using rashr...it seems to flash..but the recovery which i enter afterwards is still the same..
for the 2nd one ive placed recovery.img in the root of both internal and external storage..when using the 2nd command says...no such file or directory exists..
can this problem be rectified if we flash stock kernel thru fastboot??? and then flash the new recovery?
l2azoredge said:
ive already tried using rashr...it seems to flash..but the recovery which i enter afterwards is still the same..
for the 2nd one ive placed recovery.img in the root of both internal and external storage..when using the 2nd command says...no such file or directory exists..
can this problem be rectified if we flash stock kernel thru fastboot??? and then flash the new recovery?
Click to expand...
Click to collapse
I don't think so. what kernel are you using ? Seems your kernel ignore recovery partition....
Having the same problem after upgrading to CM 13. Any solution would be appreciated.
2- using command: dd if=recovery.img of=/dev/block/mmcblk0p11
Click to expand...
Click to collapse
Thank god this nasty hack did the trick. However I placed my recovery.img inside the /system, so my command was 2- using command: dd if=/system/recovery.img of=/dev/block/mmcblk0p11
Try to flash with minimal adb fastboot.
If not,try this method: flash your recovery as boot(fastboot flash boot recovery.img), see if it works,then flash your kernel again.
Instead of
Code:
fastboot flash recovery twrp.img
use
Code:
fastboot flash boot twrp.img
//I didn't notice that this was already said
IiroP said:
Instead of
Code:
fastboot flash recovery twrp.img
use
Code:
fastboot flash boot twrp.img
//I didn't notice that this was already said
Click to expand...
Click to collapse
Has someone tried it already? I am afraid after installing the recovery in the boot partition and something goes wrong, that then the phone will be bricked.
Might it be the afore mentioned Kernel issue? My Xperisa XP has the kernel: 3.4.0-perf-g4c8352f-00783-gce6e17b
Thx for replies.
[EDIT]
Installing TWRP in boot partition worked fine. Let us see how it works with an Update.
The same problem
I have the same problem. Maybe Sony didn't create a recovery partition on this Phone, I unlocked it in 2016 and now i don't remember how i did this.
I only can flash boot, but afeter install system from twrp or cwm, this recovery disappear so i can't install gapps.
My experience with "Partition Not Found" is:
1.- Install Stock Rom, later of install Root
2.- Install TWRP with CMD (But the 2.8 high version, (On the internet there is a version of CMD that only makes one click and ready) Note* i Update to 3.0.1, later of install 2.8 version.
(Now update to device to Android 7, or 6, or 5)
3.- Install Rom + Gapps + Root (Note* Install Root because later u need install TWRP App)
4.- After of install rom, install TWRP App, Download and Flash Image TWRP (in the same app) on device
5.- Finally check u TWRP if all install is correct.
Saludos!
Actually i have Android 7 (Candy Rom + Fusion Kernel) with TWRP y everything is fine!
As I say in the tittle, my phone has not slot b. It means that when I try to flash any .img or .zip I have an error message telling my that "XXX_b not accesible".
How can I create the partition? I have android one and everything locked as I flashed the stock image vía COM because I have no idea how to solve the partition problem.
gfpablo_ said:
As I say in the tittle, my phone has not slot b. It means that when I try to flash any .img or .zip I have an error message telling my that "XXX_b not accesible".
How can I create the partition? I have android one and everything locked as I flashed the stock image vía COM because I have no idea how to solve the partition problem.
Click to expand...
Click to collapse
You say you are trying to flash something but then you also say that everything is locked. You can't flash anything other than the stock firmware (in EDL mode) if your bootloader is locked.
Catsonvi said:
You say you are trying to flash something but then you also say that everything is locked. You can't flash anything other than the stock firmware (in EDL mode) if your bootloader is locked.
Click to expand...
Click to collapse
I tried to flash it when i have everything unlocked. I tried to flash ASOP v6.6 and the result was a bricked phone. However I flashed the android one stock ROM and locked everything with the Xiaomi flash program.
You need to flash stock through EDL
Nebrassy said:
You need to flash stock through EDL
Click to expand...
Click to collapse
That's what i've done. Although, if I try to flash TWRP from fastboot I have an error message telling me that I have no slot b
gfpablo_ said:
That's what i've done. Although, if I try to flash TWRP from fastboot I have an error message telling me that I have no slot b
Click to expand...
Click to collapse
You can't flash the TWRP image from fastboot, since our phone does not have a seperate recovery partition and you also cannot flash ANYTHING (other than stock via EDL) if your phone's bootloader is locked.
Now since it seems that your bootloader is locked, you need to enable developer options first and then in developer options enable the "OEM unlocking" option. After that you need to go to fastboot in order to unlock the bootloader and use these commands one at the time:
fastboot flashing unlock
fastboot flashing unlock_critical
Keep in mind that after using these commands you will get a prompt on your phone to confirm that you want to unlock the bootloader and doing so will erase everything (basically like doing a factory reset).
After you fully unlock the bootloader, in order to flash TWRP with stock you need to go to the official TWRP website and find the .img and the .zip installer for the Mi A2. You need to boot the .img via fastboot with fastboot boot *location to the .img* (without the asterisks) and then transfer and flash the TWRP .zip installer with TWRP. After that you can boot into TWRP normally without fastboot booting.
If you want to flash a custom ROM you will still need to fastboot boot into the TWRP .img because the .zip you flashed is tied to the system, and since you need to wipe the system before flashing a custom ROM you will also wipe the flashed TWRP.
I still recommend reading this guide: https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
[SOLVED]
Catsonvi said:
You can't flash the TWRP image from fastboot, since our phone does not have a seperate recovery partition and you also cannot flash ANYTHING (other than stock via EDL) if your phone's bootloader is locked.
Now since it seems that your bootloader is locked, you need to enable developer options first and then in developer options enable the "OEM unlocking" option. After that you need to go to fastboot in order to unlock the bootloader and use these commands one at the time:
fastboot flashing unlock
fastboot flashing unlock_critical
Keep in mind that after using these commands you will get a prompt on your phone to confirm that you want to unlock the bootloader and doing so will erase everything (basically like doing a factory reset).
After you fully unlock the bootloader, in order to flash TWRP with stock you need to go to the official TWRP website and find the .img and the .zip installer for the Mi A2. You need to boot the .img via fastboot with fastboot boot *location to the .img* (without the asterisks) and then transfer and flash the TWRP .zip installer with TWRP. After that you can boot into TWRP normally without fastboot booting.
If you want to flash a custom ROM you will still need to fastboot boot into the TWRP .img because the .zip you flashed is tied to the system, and since you need to wipe the system before flashing a custom ROM you will also wipe the flashed TWRP.
I still recommend reading this guide: https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Click to expand...
Click to collapse
Thank you! I have to admit that I have no idea of whats wrong earlier. This guide solved the problem tho.