Related
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.
Hi,
I tried for hours installing a custom onto the P880 (rooted Android 4.0.3). It doesn't work.
I cannot boot to fastmode. None of the commands I found works:
Code:
adb reboot bootloader
adb reboot-bootloader
adb unlock-oem
When I use them, the phone will just reboot.
I managed to install CWM 6.0.1.1 (with the app "LG 4X Recovery") but I get a "Status 7" error. I tried to fix it by editing the updater-script but that didn't help.
So I tried to install a newer CWM with the ROM Manager or the TWRP with the TWRP Manager. Both failed.
Do you have any ideas what I can do?
Thank you!
Simon
I have no freakin idea where I got this file from but I'm sure I used it to unlock my BL.
Download the file, extract it,
Make sure ADB is enabled in options > developer options.
run cmd.exe as ADMINISTATOR.Type cd <directory where extracted rar is at (e.g. cd E:\P880_JB_UnLockBL\)>
Code:
adb shell
adb reboot bootloader
fastboot oem unlock
Enter each command above seperately.Make sure adb shell works, otherwise try to install the included driver first.Do a reboot of your PC & phone both after driver installation and try these steps again.
File :
http://puu.sh/dLue4/ca5507324a.rar
You can't install rom or recovery or unlock bootloader with android 4.0.3.You must unroot,update to 4.1.2 and try again!Just download lg update tool from the LG's p880 site and install stock 4.1.2 and try again to root,unlock,install recovery and tjen rom.
Good Luck
Can't update
Thank you for the fast answers but I cant't update the phone with the LG mobile support tool because there appears an error after 5%.
What can I do?
what is current status of your device at the moment?
is 4.03 ICS ok? root is ok? CWM? what version?
gtdaniel said:
what is current status of your device at the moment?
is 4.03 ICS ok? root is ok? CWM? what version?
Click to expand...
Click to collapse
Android 4.0.3 (I want 4.4)
CWM 6.0.1.1
I just unrooted the phone because I tried to update it.
ok
so far, so good.
next step is update to JB.
what you try?
gtdaniel said:
ok
so far, so good.
next step is update to JB.
what you try?
Click to expand...
Click to collapse
sure thanks for your help...
what method you try to update to JB?
After booting in fastboot mode failed, I tried to update the phone with the LG mobile support tool.
ok. you can bring the phone in S/W Update mode (via reboot - vol down+USB Cable)?
PC see phone corectly (drivers is installed ok)? ADB interface appear and works in Device manager?
how about this method? http://forum.xda-developers.com/showthread.php?t=2069723
flying.toaster said:
After booting in fastboot mode failed, I tried to update the phone with the LG mobile support tool.
Click to expand...
Click to collapse
First thing you should do is upgrading to JB, becuase in ICS we are unable to unlock bootloader. For upgrading should official LG software should work good.
Hello today I am going to share you how to install stock rom in asus zenfone 4 using raw file
first you must install these :
Intel Usb Driver: http://d-h.st/VfO
Asus Flash Tool Installer: https://yadi.sk/d/K5UINtv9e9ehP
Asus zenfone 4 raw file: http://www.mediafire.com/download/prtp8p7ok6s9izf/Zenfone+4+V4.3.10.raw
After you install, follow my steps carefully
1.boot your phone into droidboot by pressing power + vol up
2.In your pc open asus flash tool
3.In asus flash tool choose model (P400CG) Wipe data (yes) and choose the raw file
http://s10.postimg.org/7ybzsv0xl/Step_1.jpg
4.plug your phone to your pc/laptop
5.after you plug your phone you will see a serial number , and click your device
http://s30.postimg.org/729moup4h/Step_2.jpg
6.start flashing
http://s27.postimg.org/shru3ater/Step.jpg
7.after flashing ,your phone will automatically reboot
8.Enjoy
Thanks guys
or just place raw file in ext sd card and perform SD download from droidboot
Yep..
Sent from my ASUS_T00I using XDA Free mobile app
Cant make use of AFT
I am unable to select the downloaded .raw file in AFT.
the only supported formats are .img or .zip
how can I flash the stock .raw file.
nor the SD DOWNLOAD in Droidboot mode recognizes this raw.file
I have tried to download it more than 4 times thinking that file might have currupt. but same result every time.
Please help
Edit:
anyways I got to learn how to select the file but now when I connect my device to PC in droidboot mode, error message pops asking to close AFT. I can Ignore the error msg to keep it running but No device is being detected in AFT.
That error comes every time I connect or remove device from PC.
This is where I need help.
or simple suggest me a full solution o below situation:
Device ASUS ZENFONE 4_T00I
Last working firmware was Jellybean 4.2.2 (never upgraded)
Problem started: Consistent FC msgs of almost all msgs.
1. Droidboot State
Droidboot Version: 6.6.3.0
Product : WW_ZENFON
Not Rooted. No Custom Recovery
2. Device Status: Was on Stock Jelly bean and was contineously giving com.android.phone failure and other FC closure consistently , hence needed to try flasing a new rom or same version.
3. Read the forums and collected following data:
Stock Firmwares:
UL-ASUS_T00I-WW-6.6.3.0_user.zip
UL-ASUS_T00I-WW-7.4.4.0-user.zip
UL-ASUS_T00I-WW-9.9.9.0-user
Raw Firmware:
Zenfone4V4.3.10.raw
4. All the Tools required to flash the firmwares and study of methods to do so. I used WIN-XP and tools installed on the same. All Drivers installed successfully device recognizing and able to use fastboot and adb.
5.Current device status: To flash UL-ASUS_T00I-WW-6.6.3.0_user.zip
I tried following methods :
FW placed on SD Flashing started but failed everytime
Tried Fastboot flash update FW.zip method by cleaning all partitions- Failed "Problem in creating otp update file-error)
Now left with no system, no userdata or no data partitions on device.
Now trying AFT method to flash .raw firmware which I have downloaded.
AFT not at all listing up my device in Droidbot mode.
VioletR said:
I am unable to select the downloaded .raw file in AFT.
the only supported formats are .img or .zip
how can I flash the stock .raw file.
nor the SD DOWNLOAD in Droidboot mode recognizes this raw.file
I have tried to download it more than 4 times thinking that file might have currupt. but same result every time.
Please help
Edit:
anyways I got to learn how to select the file but now when I connect my device to PC in droidboot mode, error message pops asking to close AFT. I can Ignore the error msg to keep it running but No device is being detected in AFT.
That error comes every time I connect or remove device from PC.
This is where I need help.
or simple suggest me a full solution o below situation:
Device ASUS ZENFONE 4_T00I
Last working firmware was Jellybean 4.2.2 (never upgraded)
Problem started: Consistent FC msgs of almost all msgs.
1. Droidboot State
Droidboot Version: 6.6.3.0
Product : WW_ZENFON
Not Rooted. No Custom Recovery
2. Device Status: Was on Stock Jelly bean and was contineously giving com.android.phone failure and other FC closure consistently , hence needed to try flasing a new rom or same version.
3. Read the forums and collected following data:
Stock Firmwares:
UL-ASUS_T00I-WW-6.6.3.0_user.zip
UL-ASUS_T00I-WW-7.4.4.0-user.zip
UL-ASUS_T00I-WW-9.9.9.0-user
Raw Firmware:
Zenfone4V4.3.10.raw
4. All the Tools required to flash the firmwares and study of methods to do so. I used WIN-XP and tools installed on the same. All Drivers installed successfully device recognizing and able to use fastboot and adb.
5.Current device status: To flash UL-ASUS_T00I-WW-6.6.3.0_user.zip
I tried following methods :
FW placed on SD Flashing started but failed everytime
Tried Fastboot flash update FW.zip method by cleaning all partitions- Failed "Problem in creating otp update file-error)
Now left with no system, no userdata or no data partitions on device.
Now trying AFT method to flash .raw firmware which I have downloaded.
AFT not at all listing up my device in Droidbot mode.
Click to expand...
Click to collapse
You need AFT version 1.0.0.0 for RAW files. See here: http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=3567
Solved
I flashed v6.3.5.0.img.gz successfully using droidboot.
Thanx a lot.
Now i an on Lollipop v7.4.4.0 thanx for all help
Solved
Root
Does it require root permissions ? Because i have heard that flasing like this can burn the motherboard please tell ... :crying::crying:
No it can if u flash it 100or200 times
I jab flashed roms in my ZenFone 400cg 90 to 110 times either cm or zenui.. lol... nothing happened
Sent from my ASUS_T00I using XDA Free mobile app
thank you so much Techjohn9 and other guys, this thread is really helpfull...
but my navigation buttons (home, back and window toggle) are not working......
please suggest me some solutions ...
I'm using Asus zenfone 4 a400cg mobile droid version 6.6.3 WW I downloaded UL Asus tool firmware 6.6.3 WW and tried to flash error msg coming like image SKU is not match help me to solve this problem
I actually downgraded from lollipop to jellybean,flashing was successful. But the problem is now the back,home and multitask touchpads are not working. It was working fine in the lollipop version, i don't know what happened. Please help me...
I've the same problem. Do you have any remedy?
VioletR said:
I flashed v6.3.5.0.img.gz successfully using droidboot.
Thanx a lot.
Now i an on Lollipop v7.4.4.0 thanx for all help
Solved
Click to expand...
Click to collapse
Give me img v6.3.5, Please.
No man it is not working this time my mobile got stuck in bootloop
Update
mrvj123 said:
thank you so much Techjohn9 and other guys, this thread is really helpfull...
but my navigation buttons (home, back and window toggle) are not working......
please suggest me some solutions ...
Click to expand...
Click to collapse
Update your Asus Zenfone 4 > UL-ASUS_T00I-WW-6.6.3.0-user :laugh: :good:
mrvj123 said:
thank you so much techjohn9 and other guys, this thread is really helpfull...
But my navigation buttons (home, back and window toggle) are not working......
Please suggest me some solutions ...
Click to expand...
Click to collapse
bro u got any fix?
The links in the OP are absolute poison!
Are the files available from any other source?
Where can I find ASUS_BUNDLE.ZIP which droidboot requires?
Hello ! I've tried to unlock bootloader at first and succeeded in that when i was on the lollipop . Unlocking is done by the unlock tool provided by the ASUS Officials.
Then i flashed the cynogen 12.1 unofficial via a boot.img , atwrp v3.img & a system.img.
Everything was fine until i needed to revert back to stock firmware.
And also everytime when i try to boot into recovery via Power & volume (-) button , it boots into system.
I used "adb reboot recovery" to boot into twrp recovery .
So, to revert back i saw a method in which we flash a raw firmware , and i downloaded a 4.0.3 for Asus Zenfone 4.
But after flashing it , the bootloader i unlocked , got locked by itself (means i can open droid boot but cannot modify boot and recovery partition via "fastboot flash boot boot.img" & "fastboot flash recovery recovery.img" ).
I can only flash system via " fastboot flash system system.img".
I tried to unlock it on Jelly Bean but no success.
Also i tried updating the firmawre via OTA and flashing zip in recovery mode but i was not able to boot into recovery mode, even with "adb reboot recovery".
It always ends up with a reboot , then booting into a 'Android logo for 200 to 300 millisec' , & then boot into system.
Then i found a KitKat firmware raw file , but when i flashed it via AFT 1.0.0.0 , it always gives error "no space left for flashing modem binary".
I tried "fastboot erase data" ,"fastboot erase userdata" ,"fastboot erase cache" , & "fastboot erase system" , but ended up with stock rom with no modem binary.
So , i tried to unlock the bootloader again by the "unlock tool" provided by ASUS , but even after connected to a high speed Wifi , It gives connection error and rest of the other things are working fine like browser etc.
I also tried to flash the modem.zip inside the stock firmware zip via fastboot as : "fastboot flash update modem.zip. It has flashed the zip but still no modem binary.
Then i tried to flash the bin file inside the modem.zip as : fastboot flash radio radio_firmware.bin and it gives error : No space left for flashing modem binary.
Now i have a bootloader (locked) but no recovery and a stock firmware with no modem binary.
Cn to ww
Hello, I have a big issue with my zenfone4 max plus zc550tl. I received the phone with a CN rom and after update to new version I lost all languages except chinese and english and every google apps. Someone can help me? I need to change my rom from CN to WW or to recovery old Rom 18. Help!!
AlfredDispi said:
Hello, I have a big issue with my zenfone4 max plus zc550tl. I received the phone with a CN rom and after update to new version I lost all languages except chinese and english and every google apps. Someone can help me? I need to change my rom from CN to WW or to recovery old Rom 18. Help!!
Click to expand...
Click to collapse
This forum is only for Asus Zenfone 4 A400CG and A450CG; which is a 4 year old device; and should not be confused with the new Zenfone 4(s).
Hello,
I have unlocked the bootloader (paying someone).
Now that it is unlocked, how can I install TWRP?
I connect the phone to the pc, then when I type "adb reboot bootloader" the phone reboots in download mode then I type "fastboot flash recovery twrp.img" but the windows show the message "< waiting for device>" and nothing happen...
As you can imagine, I am the opposite of an expert, but is there someone who can help me .... ?
thank you
Linux or windows? If the latter, do you have drivers correctly installed?
I recommend you first read theory, find in Nokia threads etc, before flashing... this prevent you "bricking" of phone...
In Windows you must install different drivers for device in bootloader/downloader mode... try install from virtual cdrom in n7p while android booted...
Next, you try flash twrp.img to recovery partition (if this you not have from previous phone, you use bad howto, or maybe don't read howto and maybe you have bad twrp img... anyway N7p DON'T have separate recovery partition, have recovery function inside boot partition and then is need always twrp patched on EXACT boot image version for/from you actual ota/security/system version...
I sugest (also if you have correct boottwrp img, don't use patched version, but install special twrp zip installer in special only booted another twrp... here is howto:
https://forum.xda-developers.com/no...t/recovery-twrp-3-2-3-0-t3892644/post79010319
scynthero said:
Linux or windows? If the latter, do you have drivers correctly installed?
Click to expand...
Click to collapse
Windows 10.
Driver correctly installed, when I connect the phone to the pc if I type "ADB devices" my Nokia is listed correctly.
Then the guy who make the unlock remotely connected with my pc using TeamViewer and he installed all drivers to unlock the bootloader... I presume...
k3dar7 said:
I recommend you first read theory, find in Nokia threads etc, before flashing... this prevent you "bricking" of phone...
In Windows you must install different drivers for device in bootloader/downloader mode... try install from virtual cdrom in n7p while android booted...
Next, you try flash twrp.img to recovery partition (if this you not have from previous phone, you use bad howto, or maybe don't read howto and maybe you have bad twrp img... anyway N7p DON'T have separate recovery partition, have recovery function inside boot partition and then is need always twrp patched on EXACT boot image version for/from you actual ota/security/system version...
I sugest (also if you have correct boottwrp img, don't use patched version, but install special twrp zip installer in special only booted another twrp... here is howto:
https://forum.xda-developers.com/no...t/recovery-twrp-3-2-3-0-t3892644/post79010319
Click to expand...
Click to collapse
Thank you, I'll read carefully that thread and hope not to brick the phone. If I'll brick it, it would be a good chopping board... Thank for all informations!
Hello everyone. i just want to install Gsi on an new unlocked tab a8, after flashing twrp, I use the fastbootd mode to flash the gsi and installed the multi-disable zip. when I want to reboot to os, it stucked at bootlogo. I don't know where I am wrong, so please help me, in appreciation
WolfHRB said:
Hello everyone. i just want to install Gsi on an new unlocked tab a8, after flashing twrp, I use the fastbootd mode to flash the gsi and installed the multi-disable zip. when I want to reboot to os, it stucked at bootlogo. I don't know where I am wrong, so please help me, in appreciation
Click to expand...
Click to collapse
We don't know where you went wrong either because you didn't list the steps you took or what GSI you flashed or what stock ROM you started from. Or where you are looping.
starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot
lewmur said:
We don't know where you went wrong either because you didn't list the steps you took or what GSI you flashed or what stock ROM you started from. Or where you are looping.
Click to expand...
Click to collapse
starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot
WolfHRB said:
starting firmware: X200ZCU2CWD3
Steps: 1. Unlock BL
2. flash TWRP via Odin V3.14
3. Format data partition
4. flash dm-verity disabler (File name: Disable_Dm-Verity_ForceEncrypt)
5. reboot to fastbootd mode (using TWRP reboot menu)
6. fastboot erase system
7. fastboot flash system "img path"
8. fastboot -w
9. fastboot reboot
Click to expand...
Click to collapse
Don't flash dm-verity disabler for this device and the GSI should boot as long as it's compatible
kevinco1 said:
Don't flash dm-verity disabler for this device and the GSI should boot as long as it's compatible
Click to expand...
Click to collapse
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.
stradfred said:
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.
Click to expand...
Click to collapse
What exact GSI and build are you trying to install? There are only a few that are compatible, otherwise you're not gonna have any other luck flashing
I tryed with on my X200XXU2CWC1 firmware:
lineage-19.1-20230418-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230325-UNOFFICIAL-a64_bgN.img
Old version too but the same result...
Which version we are sure that works?
stradfred said:
I tryed with on my X200XXU2CWC1 firmware:
lineage-19.1-20230418-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img
lineage-20.0-20230325-UNOFFICIAL-a64_bgN.img
Old version too but the same result...
Which version we are sure that works?
Click to expand...
Click to collapse
Make sure you are only trying to flash arm64 builds for this device
Both 19.1-20230418 and 20.0-20230324 do install properly but there's certain bugs that make them unfit to be used as a daily driver.
If you're looking for the latest build where everything works (including bluetooth) flash 20.0-20230218
stradfred said:
Without this alway bootloop logo too.
1. Extract the IMG to the adb folder and rename it system.img
2. Flash TWRP with ODIN
3. When booting into TWRP using the Volume up and Power key, select reboot and then fast boot.
4. When you get there, go on your PC and open cmd with the adb folder.
5. Now type fastboot devices just make sure you have the device connect properly. Type fastboot -w after.
6. Type "fastboot flash system system.img" press enter and wait for it to finish. The last line should be be where you can type other commands.
7. When its finished, type fastboot reboot fastboot.
Click to expand...
Click to collapse
You left out the step to format data and factory wipe.
lewmur said:
You left out the step to format data and factory wipe.
Click to expand...
Click to collapse
That's right!
How is it normal to do this command after having flashed a ROM ???
Once done, I boot of course on lineage after a few moments on the Samsung logo.
Which version of lineage is the most stable, 19 (Android 12) or 20 (Android 13)?
Thank you both for your help.
kevinco1 said:
If you're looking for the latest build where everything works (including bluetooth) flash 20.0-20230218
Click to expand...
Click to collapse
https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/History/lineage-20.0-20230218-UNOFFICIAL-arm64_bgN.img.xz/download
I tried this.
stradfred said:
That's right!
How is it normal to do this command after having flashed a ROM ???
Once done, I boot of course on lineage after a few moments on the Samsung logo.
Which version of lineage is the most stable, 19 (Android 12) or 20 (Android 13)?
Thank you both for your help.
Click to expand...
Click to collapse
TWRP and fastboot can't handle the encrypted data partition. So you need to format it. Current versions of LOS re-encrypt it as soon as you boot to system. And you can't use dm-verity on this model, so you can't disable it.
stradfred said:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/History/lineage-20.0-20230218-UNOFFICIAL-arm64_bgN.img.xz/download
I tried this.
Click to expand...
Click to collapse
Did you try this build before or after the realization you had left out the steps to wipe and factory reset?
Has anyone managed to install a GSI on the SM-X200 with X200XXU2CWC1 firmware? I tried different LOS 20 and LOS 19 GSIs, with and without GAPPS, including the ones mentioned earlier from March and April, but did not succeed a single time. The tablet gets always stuck in a boot loop. I flashed via TWRP and wiped and formatted data every time.
Is it possibly the vendor firmware (SW rev. 2) that prevents the GSI from running? All guides from this forum seems to relate to a SW rev. 1 firmware like X200XXS1CWA3.
mrspeccy said:
Has anyone managed to install a GSI on the SM-X200 with X200XXU2CWC1 firmware? I tried different LOS 20 and LOS 19 GSIs, with and without GAPPS, including the ones mentioned earlier from March and April, but did not succeed a single time. The tablet gets always stuck in a boot loop. I flashed via TWRP and wiped and formatted data every time.
Is it possibly the vendor firmware (SW rev. 2) that prevents the GSI from running? All guides from this forum seems to relate to a SW rev. 1 firmware like X200XXS1CWA3.
Click to expand...
Click to collapse
If you mean you used the "Install" button in TWRP to flash, then that is your mistake. The "Install" button only has the option to flash the "Super" partition and not the "System". You need to use "Fastboot" to flash the system image. I flashed from CWD2 which is even later than CWC1, so that shouldn't be a problem. If it was, then TWRP wouldn't have worked. I'm running LOS 20 20300507 bgN.
No, I used TWRP to get into fastboot mode and said fastboot flash system ...img. I have no idea what I did wrong. Previously I flashed Lineage on a couple of Samsung Tablets (SM-T510, SM-T505).
mrspeccy said:
No, I used TWRP to get into fastboot mode and said fastboot flash system ...img. I have no idea what I did wrong. Previously I flashed Lineage on a couple of Samsung Tablets (SM-T510, SM-T505).
Click to expand...
Click to collapse
There are only certain LOS builds that work with this device, you're wasting your time if you are blindly flashing random ones.
Refer to earlier posts to confirm which ones do work. And like @lewmur just reported the newest build 20300507 bgN does flash successfully
The 20230507 bgN was actually the first build I tried before I went to older variants, including the 20220814 bgN that is mentioned in a different thread.
@lewmur : Did you do a clean flash and format data before you installed the 20230507 build on the CWD2 firmware? There might be some issues with format data and the TWRP 3.7.0-12.2 from this forum (https://forum.xda-developers.com/t/...-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691/) on the latest kernel. After I format data in TWRP, the tablet is recognized as writable media in Windows, but I get reading and writing errors when I try to access the about 22 GB large partition.
I know that it is impossible to roll back the bootloader to revision 1, but may it be possible that I extract and flash a kernel from the X200XXS1CWA3 to further investigate this issue?
mrspeccy said:
The 20230507 bgN was actually the first build I tried before I went to older variants, including the 20220814 bgN that is mentioned in a different thread.
@lewmur : Did you do a clean flash and format data before you installed the 20230507 build on the CWD2 firmware? There might be some issues with format data and the TWRP 3.7.0-12.2 from this forum (https://forum.xda-developers.com/t/...-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691/) on the latest kernel. After I format data in TWRP, the tablet is recognized as writable media in Windows, but I get reading and writing errors when I try to access the about 22 GB large partition.
I know that it is impossible to roll back the bootloader to revision 1, but may it be possible that I extract and flash a kernel from the X200XXS1CWA3 to further investigate this issue?
Click to expand...
Click to collapse
You must do a clean flash. The purpose of formatting the data partition is to get rid of the encryption. TWRP can't handle the encryption. And LOS will re-encrypt it the first time you boot to system. As to extracting the kernel from CWA3, I don't advise doing that. It could hard brick the tablet.