I followed this instruction https://wiki.lineageos.org/devices/gta4xl/install
and I wrote the wrong recovery file, which is the Samsung S6 Lite (LTE) recovery to my Samsung Tab A7 Lite (LTE)
and now it keeps boot looping can someone help with this is there any way to fix this
It keeps boot looping
Ok I got it fixed by flashing another firmware into it using odin4 which can be found here[linux]:
OFFICIAL Samsung Odin v4 1.2.1-dc05e3ea - For Linux
Try out my new Linux flash tool called Thor - https://forum.xda-developers.com/t/dev-thor-flash-utility-the-new-samsung-flash-tool.4597355, which has all the features of this tool + extras, like the usual Windows Odin ones which are missing in...
forum.xda-developers.com
I downloaded the firmware from samfw.com by searching the apppropriate model(SM-T225) and firmware
I extracted the downloaded zip then used the following command after switching my tablet to download mode:
sudo odin4 -b BL_T225XXU3CWD1_T225XXU3CWD1_MQB64111985_REV00_user_low_ship_MULTI_CERT.tar.md5 -a AP_T225XXU3CWD1_T225XXU3CWD1_MQB64111985_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS13.tar.md5 -c CP_T225XXU3CWD1_CP24050499_MQB64111985_REV00_user_low_ship_MULTI_CERT.tar.md5 -s CSC_ODM_T225ODM3CWD1_MQB64111985_REV00_user_low_ship_MULTI_CERT.tar.md5 -d [device usb bus (ex: "/dev/bus/usb/001/015" )]
Click to expand...
Click to collapse
also the AP, CP, CSC and BL files most probably will be named differently so make sure to check that as well.
And that fixed it for for, hope that does so for anyone else facing the same issue.
SideNote: Dont forget you need to have your tablet connected via USB to open download mode which is Vol UP + Vol DOWN ( NO POWER BUTTON), and do this when the display goes for the few seconds while boot looping
Related
So I've been playing around with the Nexus Q, trying to build custom ROMs for it, but ran into a bit of a snag last night when I flashed a new kernel and somehow lost xloader and uboot. Luckily for us Google was kind enough to leave a flag on in the hardware that boots up the device into diagnostic mode for 2 seconds prior to loading xloader (if it can). When you plug the device into your computer and then power it on you'll always see a new device pop up called "OMAP4440" very briefly. This is the serial console that the CPU sets up to allow flashing when the flasher (fastboot) is broken.
In order to use this emergency recovery mode you'll need to download the OMAPFlash application that can be found here: http://goo.gl/iRvRk
That package contains drivers for the OMAP4440 device (the driver is labeled OMAP 4460 when you install it) and installing it can be a bit tricky. Since you only have 2 seconds to install the driver you'll have to have the Device Manager open and ready to double click on the OMAP4440 device as soon as it pops up. From there you can click Update Driver and install it from the usb_drv_windows folder. The device will go offline while you're in the process but when you plug it back in again Windows should find the driver you just installed. NOTE: I had some problems with Windows trying to search Windows Update even after installing the driver and had to click on the cancel link in the driver installation dialog.
Now that you've got the driver installed we can use OMAPFlash to get the Q back into a working state. The package I linked to above contains definitions for the Galaxy Nexus (tuna) but just so happen to work on the Nexus Q. In a Command Prompt run the following command in the directory you extracted the files:
Code:
omapflash -v -t 60 -2 -p OMAP4460_TUNA_8G_HS_ENG fastboot
An explanation of the flags:
-v = Verbose
-t 60 = Timeout: 60 seconds
-2 = Upload and execute the 2nd boot ROM
-p OMAP4460_TUNA_8G_HS_ENG = Device configuration (8G = 1GB of RAM)
fastboot = Boot the device into fastboot mode
Run the command then plug in the device. OMAPFlash will see the device come online and send the 2nd boot ROM to boot it into fastboot mode. If everything goes well your Q will turn completely red and you'll now have a fastboot device plugged in to your system.
From here "fastboot flash" all the partitions to restore your device to its former glory (using the img files from the factory ZIP):
Code:
fastboot flash xloader xloader-phantasm-ian67k.img
fastboot flash bootloader bootloader-phantasm-steelheadb4h0j.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
My lesson learned: don't flash the "boot" partition until you've tested it first with "fastboot boot boot.img"
Great work! Does this work with the gnex too?
animal24 said:
Great work! Does this work with the gnex too?
Click to expand...
Click to collapse
The instructions and OMAPFlash package were actually taken from a GNEX thread (the GNEX is nick-named "tuna" )
OP updated to include a working download URL.
Great to know, maybe it could be useful for Glass
Sent from my HTC One using Tapatalk 4 Beta
Help Please?
I had my Galaxy Pocket rooted and got the Jellyblast v3 rom, it was doin fine until I checked on the app OTA and check for update, a new update appeared which is the Nemesis 2.5 Hybrid-Holo Editon. It asked me to download it and so I did. When it was done, it asked me if I wanted to install it and so I did, and rebooted. Later I noticed that it was already boot looping. I tried pulling the battery off and to clockwork mode, with the proper procedure..the holds and presses, but still it just kept boot looping. Tried to connect it to the PC using the USB chord and yet it just shows the charging icon and sooner it turns to white. I tried Kies but still it turned white screen all over again; no device found.
Can someone PLEASE help me with this one? PLEASE, PLEASE guys? I know you guys are knowledgable on these kind of issues. :crying:
ShogunSam said:
Help Please?
I had my Galaxy Pocket rooted and got the Jellyblast v3 rom, it was doin fine until I checked on the app OTA and check for update, a new update appeared which is the Nemesis 2.5 Hybrid-Holo Editon. It asked me to download it and so I did. When it was done, it asked me if I wanted to install it and so I did, and rebooted. Later I noticed that it was already boot looping. I tried pulling the battery off and to clockwork mode, with the proper procedure..the holds and presses, but still it just kept boot looping. Tried to connect it to the PC using the USB chord and yet it just shows the charging icon and sooner it turns to white. I tried Kies but still it turned white screen all over again; no device found.
Can someone PLEASE help me with this one? PLEASE, PLEASE guys? I know you guys are knowledgable on these kind of issues. :crying:
Click to expand...
Click to collapse
I also received the same message and downloaded the update file. when ask to Reboot & Install i selected install the device booted in CWM and i selected update from .zip and selected the downloaded file in OTA Download Folder.
The update was successful, yet the ROM looks in BETA version.
Following are the issues i am currently facing in the updated ROM
1. Gallery ICS was Force Closed, later it was solved via uninstalling update.
2. Quick Panel, Nemesis Hub, Nemesis Owner Info & Nemesis Sound Boosters are giving FC messages.
3. OTA is giving INVALID ROM Message while updating.
I´m having the same issues.
After downloading and installing the OTA update, my device is keep stucking in the boot loop.
When I do to the recovery, I always get automatic update with the update.zip, which means I can't get into the full recovery to select another functional image.
Well I hope it's not bricked. Is there a sollution?
Thanks
I have repaired that throught ODIN MODE, like described here:
http://forum.xda-developers.com/showthread.php?t=1921421&highlight=s5300
ShogunSam said:
Help Please?
I had my Galaxy Pocket rooted and got the Jellyblast v3 rom, it was doin fine until I checked on the app OTA and check for update, a new update appeared which is the Nemesis 2.5 Hybrid-Holo Editon. It asked me to download it and so I did. When it was done, it asked me if I wanted to install it and so I did, and rebooted. Later I noticed that it was already boot looping. I tried pulling the battery off and to clockwork mode, with the proper procedure..the holds and presses, but still it just kept boot looping. Tried to connect it to the PC using the USB chord and yet it just shows the charging icon and sooner it turns to white. I tried Kies but still it turned white screen all over again; no device found.
Can someone PLEASE help me with this one? PLEASE, PLEASE guys? I know you guys are knowledgable on these kind of issues. :crying:
Click to expand...
Click to collapse
I have the exact problem. I just can not do anything.No connection to PC I dont know what to d.o Did you solve the problem ShougunSam?
I get the exact same error, and its annoying because I cant use my phone! If anyone can help us.. thanks
Rawhabbero said:
I get the exact same error, and its annoying because I cant use my phone! If anyone can help us.. thanks
Click to expand...
Click to collapse
For all the SGY Users who are facing issues after updating Jellyblast 3.5 to Nemesis (I faced it too) here is the guide to recover your phone:-
First to repair your phone you have to flash stock rom via odin .
Here's the guide for Flashing Stock Rom via Odin
Requirement: 1. A Samsung Galaxy y phone model gt-s5360.
2. A computer running on windows xp, vista, win7 or win8 with proper USB driver installed to connect your phone to computer {If you have not installed USB Driver for Samsung Galaxy Y then to Install USB Driver}
3. Stock Rom file : you can download stock rom according to your choice and region from the xda thread http://forum.xda-developers.com/showthread.php?t=1465800e
4. download ODIN: 1 .85.(google it as i cannot post outside links)
Installation Instruction : [ Charge your phone battery min 80%]
1. Download the required file Odin AND Stock Rom. zip and place in a folder on your desktop .
2. Now extract both with any file extractor.-- Odin v1 .85 .zip and the stock rom zip( file which contains the stock rom i. e 2 .3 .6 )
After that extract Stock Rom file after unzipping you will get three files :
PDA _S5360 _DDLK2.tar,
MODEM_ S5360 _DDLK2.tar &
CSC_S 5360 _DDLK2 .tar
3. Now turn off your Galaxy Y {Remove the battery for 5 -10 seconds and insert it back }
4. Go to Download Mode by Pressing Volume down + Home + Power for 5- 10 sec to boot in Download Mode
5. Now you entered in Download mode select continue by pressing Volume up button .
6. Now attach/ connect your phone to computer via USB cable .
7. Now on your computer open Odin v 1 .85. exe
8.Now make sure you are getting yellow box in ID:COM ( this means that your device is now connected and detected by odin )
9.Now Select those 3 files u download before
PIT - "totoro_0623.pit"
BOOTLOADER - "BOOT" file.
PDA - "PDA" file.
PHONE - "MODEM" file.
CSC - "GT-s5360- MULTI-CSC" file.
10.Now clik on start .
And let be ODIN do its work and wait till you see PASS in green colour it mean the flashing process is complete successfully . Samsung
11.Remove your phone from pc 12.Galaxy Y will auto reboot .
Now if you want to install nemesis Rom, you have to install the nemesis Rom 2.0 (Nemesis Titanium) first and than you should update the Rom by downloading the update file via OTA and flashing the zip file through CWM.
I hope my suggestion will solve your problem.
Did you wipe data and wipe catch before installing ROM??
Did you try flashing original ROM with Odin or others??
---------- Post added at 07:53 PM ---------- Previous post was at 07:48 PM ----------
chaos titan said:
did you wipe data and wipe catch before installing rom??
did you try flashing original rom with odin or others??
Click to expand...
Click to collapse
plz reply
thanks
thepain20 said:
For all the SGY Users who are facing issues after updating Jellyblast 3.5 to Nemesis (I faced it too) here is the guide to recover your phone:-
First to repair your phone you have to flash stock rom via odin .
Here's the guide for Flashing Stock Rom via Odin
Requirement: 1. A Samsung Galaxy y phone model gt-s5360.
2. A computer running on windows xp, vista, win7 or win8 with proper USB driver installed to connect your phone to computer {If you have not installed USB Driver for Samsung Galaxy Y then to Install USB Driver}
3. Stock Rom file : you can download stock rom according to your choice and region from the xda thread http://forum.xda-developers.com/showthread.php?t=1465800e
4. download ODIN: 1 .85.(google it as i cannot post outside links)
Installation Instruction : [ Charge your phone battery min 80%]
1. Download the required file Odin AND Stock Rom. zip and place in a folder on your desktop .
2. Now extract both with any file extractor.-- Odin v1 .85 .zip and the stock rom zip( file which contains the stock rom i. e 2 .3 .6 )
After that extract Stock Rom file after unzipping you will get three files :
PDA _S5360 _DDLK2.tar,
MODEM_ S5360 _DDLK2.tar &
CSC_S 5360 _DDLK2 .tar
3. Now turn off your Galaxy Y {Remove the battery for 5 -10 seconds and insert it back }
4. Go to Download Mode by Pressing Volume down + Home + Power for 5- 10 sec to boot in Download Mode
5. Now you entered in Download mode select continue by pressing Volume up button .
6. Now attach/ connect your phone to computer via USB cable .
7. Now on your computer open Odin v 1 .85. exe
8.Now make sure you are getting yellow box in ID:COM ( this means that your device is now connected and detected by odin )
9.Now Select those 3 files u download before
PIT - "totoro_0623.pit"
BOOTLOADER - "BOOT" file.
PDA - "PDA" file.
PHONE - "MODEM" file.
CSC - "GT-s5360- MULTI-CSC" file.
10.Now clik on start .
And let be ODIN do its work and wait till you see PASS in green colour it mean the flashing process is complete successfully . Samsung
11.Remove your phone from pc 12.Galaxy Y will auto reboot .
Now if you want to install nemesis Rom, you have to install the nemesis Rom 2.0 (Nemesis Titanium) first and than you should update the Rom by downloading the update file via OTA and flashing the zip file through CWM.
I hope my suggestion will solve your problem.
Click to expand...
Click to collapse
IT STILL DOES NOT WORK! I flashed the device, and this is what i get every time! WHAT AM I DOING WRONG?
This is an guide for when you bricked your ZTE Blade V9, or you destroyed OS without being able to flash with recovery mode(go to step 9).
There are some hacked webservers with articles and shady downloadlinks about this topic, use brain.
I think it can work with an locked oem, because i locked it at some piont earlier.
If your phone isnt showing up as device, give it 1-2 minutes.
Your Phone works even when its showing a black screen.
You do that on your own risk, Iam no ZTE developer.
1. Read the guide, know what you are doing.
2. Download "ZTE Terminal Software", "adb,fastboot,emmc", "ZTE drivers", Stock Rom (update.zip).
Also some "aboot" chinese-factory-testing-firmware which at least gets the phone booting (emmc_appsboot.mbn) from unofficialtwrp at page zte-blade-v9-twrp-3-2-root.
3. Prepare you stock system.img file from the stock rom to flash later. Get an dat to img converter (I used sdat2img.py [email protected]) and extract the img. Rename it to system.img.
4. Boot phone in download mode, the display may be dark but its there ... depends on your damage. Power + Vol- (If it wont work, try starting it normally)
5. Run PortManager from Terminal Software.
6. See COM4(DIAG) -> if anything other adjust drivers in Device Manager. "ZTE 3G Phone AT" should be the right one. There are also some Qualcomm usb drivers which work.
7. Select Port from PortManager as LINE1 USB in "ZTE Terminal Software".
You should now see COM3(DIAG) in ZTE Terminal Software.
8. Use emmcdl on COM3 to flash. Exclude recovery if you have a working/modded one.
I used the original recovery from the stock rom. (emmcdl -p COM3 -f prog_emmc_firehose_SDM450.mbn -b aboot emmc_appsboot.mbn & emmcdl -p COM3 -f prog_emmc_firehose_SDM450.mbn -b recovery recovery-orig.img)
9. Boot phone in recovery mode. Power + Vol+
10. Select "Reboot to bootloader".
11. Find your phone in ">\ fastboot devices".
12. Get the flashscript from file "\META-INF\com\google\android\updater-script" in the stock firmware "update.zip".
Get all extract commands like "package_extract_file("lksecapp.mbn", "/dev/block/bootdevice/by-name/lksecapp");" ;
13. Transfer them into fastboot flash commands and reflash all partitions. (exclude recovery if you have a working/modded one)
Flash your system.img file (step 3) to "system" .
If needed do the same with "vendor".
14. unlock oem.
15. Try restarting your Phone.
16. ???
17. Success !
18. Disable any updates from ZTE, update 1.4 will go good but 1.5 bricks the phone.
18.2 I updated to 1.5 and bricked the phone, because its a "mayor update".
18.3 Follow steps 4 to 8 and only flash the emmc_appsboot.mbn from the STOCK ROM .
19. Do a backup.
Known bugs:
- Wifi cant start -> try reflash (flash system first or including "vendor") or use simcard and hope that ZTE Android update will fix it.
- oem seems locked and unlocked at the same time - ?
Greetings
-deleted-
Background
Samsung Galaxy A3-2017 SM-320Y model only able to boot on Download Mode. i have no windows machine, only Debian linux PC. This is 2019 and the phone is Two Years old. Probably no many people using for daily gadget. However some "Small screen Lovers" have no many choice today. Thus this phone is still valuable.
Tools
- Working Debian linux pc with minimal android tools installed : adb, fastboot and Heimdall ( Odin friend on linux ), lz4 archive tools.
Note : working to poke android device, required extra effort in linux.
Download any stock rom for your device from any source. But i provide ready for use for SM-320Y indonesian Rom : Download via Mega
Extract to any path you have write access.
Connect SM-320Y on Download mode via USB port and in terminal navigate to the folder which downloaded file extracted > i.e ~/sm-320y/$
Code:
1. ~/sm-320y $ ls
to ensure you have required files :
boot.img
cache.img
cm.bin
hidden.img
modem.bin
param-stock.bin
recovery.img
sboot.bin
system.img
userdata.img
All this files are extracted from stock rom [B]XID-A320YDXU3CRL3-20190104155058[/B]
added other files : twrp-3310-sm320y.img ( I got from this forum), param-android.bin and param-jonsnow.bin just for fun
2.Flash SM-320Y with oreo stock rom by heimdall with the following command
~/sm-320y $ heimdall detect
this is to ensure that connection between phone and pc is working well, if the out put is [B] device detected [/B] then you are safe to proceed
~/sm-320y $ heimdall flash [B]--BOOTLOADER sboot.bin --CACHE cache.img --USERDATA userdata.img --RADIO modem.bin --HIDDEN hidden.img --CM cm.bin --PARAM param-stock.bin --RECOVERY recovery.img --SYSTEM system.img --BOOT boot.img --no-reboot[/B]
if you wish the phone reboot after flashing --no-reboot command is not needed.
Upon device reboot : you will have working SM-320Y with completely oreo stock rom. if you were satisfy with this. the device is usable for daily driver.
Small Fun
If you flash --PARAM partition with file param-android.bin you will get black boot splash with ANDROID letters if you choose param-jonsnow.bin you will get Jon Snow as boot splash replacing stock boot splash.
Next Fun
I do not like bloated device with too many google and samsung stuffs which I did not use them. I found THIS A3-2017 XDA THREAD by XDA Member @potoilo Thanks to him for cooked oreo fast, minimum, debloated rom.
Discusssion
Target is run SM-320Y on fast, debloated, minimal rom. The guide by Potoilo is easy to understand, however for noob, this not so easy sometimes. Start from SM-320Y live with oreo stock rom.
Set device a developer option, OEM unlock, debugging and stuffs.
Boot into download mode (FROM device OFF ) push and hold Vol Down, Power and Home Buttons simultaneously, look like we need our both hands.
Connect device on download mode to PC and again we will need heimdall help.
Open terminal on pc and do standard check with command >
Code:
$ heimdall detect
$ heimdall flash --RECOVERY twrp-3310-sm320y.img [COLOR="Red"]--no-reboot[/COLOR]
this --no-reboot option is [B]Mandatory[/B] in this case to prevent the device rebooting itself after flashing as heimdall default behaviour.
Switch off device (from Download Mode) by push and hold Vol Up, Vol Down, Power and Home Buttons simultaneously.
Once device OFF, Released Vol Down button while Vol Up, Power and Home Buttons still pushed and hold. > device will boot in TWRP Recovery mode (should be Yellow color ).
On some case, data is not accessible by TWRP, thus good idea to wipe ( Factory reset option ) and reboot to Recovery TWRP again.
Connect device (in recovery mode) to PC and ceck with terminal command > adb devices, upon device recognized it is good to proceed.
As instructed to put oreo minimal stock room by Potoilo, we need to put extracted rom file to device at /sdcard/TWRP/Backups folder.
In PC create a folder named Backups > put Potoilo extracted file to this folder then > we can create with file explorer in PC for less hazzle.
Open terminal and navigate to path where folder named Backups exist
Code:
$ adb push Backups /sdcard/TWRP/
adb will send folder Backkups to phone
Optional, reboot device to recovery again.
Follow the guide at Potoilo thread in installing Potoilo rom to device with Restore/ option
Have nice tweaking
hi, i flashed the wrong twrp on my a20e and now it can't get into fastboot or recovery either, it just sits still on the teamwin logo every time that i power it, it also doesn't get recognized on my pc, i suppose it is hard bricked but is there a way?
if not, well i tried it.
(IMPORTANT THESE STEPS INSTALL THAT SAMSUNG SYSTEM AND THAT RECOVERY OF SAMSUNG)
(IMPORTANT I am not responsible if it doesn't work for you)
Download and install the firmware
Step 1. Install "Frija" (https://github.com/SlackingVeteran/frija/releases)
Step 2. Open Frija. (Model: SM-A202F | CSC (List of all CSC https://www.droidviews.com/how-to-change-csc-in-samsung-galaxy-phones/))
Click Check Update, and then click Download.
Wait for the file to finish and unzip the file
Step 3. Download your USB driver and install the USB driver (https://gsmusbdriver.com/samsung-sm-a202f).
Step 4. Shut down your phone while holding the volume up and down and plug in the charger while holding it down
(It is important that the cable is connected to your PC.)
Step 5. Download and launch Odin (https://www.androidweblog.com/download-odin-flash-tool-windows/).
Step 6.
Now select the firmware that you downloaded in step 2
BL + AP + CP + CSC (CSC = CSC not HOME_CSC) (if it doesn't work, give it a try with HOME_CSC)
Step 7. Click on flash