oh man, my stupidity has done it again.
i did these stupid things below by short:
sm n910g sintel from singapore
last build is 5.0.1 N910GDTU1BOF1
the recently update to 6.0.1 N910GDTU1DPG4
no good
downgrade to 5.1.1 N910GDTU1DPG4
successfull
still no good
want to try dr ketan m6 custom rom
upgrade to 6.0.1 again using smart switch
device stuck in recovery loop
downgrade again with odin but failed
then stuck in firmware upgrade failed screen
can't load stock recovery
can load download mode
try flash cutom twrp & cwm recovery for 6.0.1 since the downgrade failed
can manage to start up recovery of each version
but getting mount /system error
now the device won't boot into tw ui
only can but into twrp/cwm recovery
what should i do now?
please help out
many thanks to you
------------------------------------------------------
since i don't know how to use adb to push file trough twrp
i use micro sd card to flash dr ketan's m6 rom
i factory wipe in cwm
then i install by ext sd following the insturction given in dr ketan's thread
this time i manage to go through samsung galaxy note 4 logo and to samsung logo and the logo is now blinking with the uper right hand light
still not sure if it's under looping cause just 2 minute is wrote this status, still waiting
i notice when in galaxy note 4 logo, i saw there is yellow santance in the top left
saying firmware bit and kernel bit
what does that mean?
-------------------------------------------
currently the device is in apps installing page
i think the installation is a success, is it?
still waiting it to be fully usable
-------------------------------------------
yes!!!
it was a success!!!
currently i'm running dr ketan m6 on my n910g
it's so smooth
but one thing here
before i flash this rom
i did the facrtory reset in the cwm
now that the rom is install, and the esential update that comes with it is installed too
should i go for another factory wipe?
if so, which factory wipe should i choose?
the one in cwm or the one in the m6 system?
-----------------------------------
device is kind of burning now
i wonder is it that i choose to restore all the apps from previous firmware
all 69 apps of them......
-----------------------------------
Uptill now the using experience of Dr ketan m6 is quite good
But still facing a bit laggy while wake up from sleep state
And wired thing is lock screen uses two step
First scroll page to enter password page (eg, draw pattern)
At this point it's gone laggy, for maybe 1~3 time to try to unlock the phone again
Just now I faced this problem again, I think it might be the cache problem
So I try to go in to recovery using power button long press > restart > recovery
But strange thing happen
I can't boot in to recovery
It shows "sbl1 partition doesn't exist"
I haven't try download mode yet
But do I have to Odin again for the custom recovery (cwm) to be use in the future?
You haven't mentioned trying wipes or factory reset. That may be the cause of not booting system when you downgraded.
Unable to mount system in recovery is concerning though. Could possibly be eMMC corruption or hardware failure? But did you make sure the reactivation lock was off? The fact that you were able to flash in Odin successfully suggests it was off to start with but did you enable it afterwards? Read your phone's display while in download mode for reactivation lock status. If unlocked, the focus should be on flashing the right tar- like the one that matches your data.
Did the downgrade with Odin attempt to flash an older tar not compatible with bootloader? (You can't flash full tars like Android 5.0 or KitKat in Odin).
It may be wise to Odin flash the last stock tar that actually booted and matches your data if you haven't wiped it. Or flash the tar you want- as long as it's allowed- and factory reset in stock recovery and Odin the tar again.
But, if you did enable reactivation lock, you should Odin the full tar that matches your point of lock. You would also need to allow it to auto boot and sign in with same Google user and password.
If still having issues or tried all of that already, I haven't mentioned that you should wipe internal memory with TWRP or CWM. If you've had CM on the phone, you should wipe internal memory before stock tar flash. One thing I prefer to do with stock tars is flash them cleanly: backup first, then wipe everything but extSdCard, power down, pull battery. Wait at least 30 seconds, discharge the power circuit by gently pressing and holding power button with battery removed. Install battery and boot to download mode to flash stock tar with latest Odin and Odin defaults.
Sent from my SM-N910P using Tapatalk
samep said:
You haven't mentioned trying wipes or factory reset. That may be the cause of not booting system when you downgraded.
Unable to mount system in recovery is concerning though. Could possibly be eMMC corruption or hardware failure? But did you make sure the reactivation lock was off? The fact that you were able to flash in Odin successfully suggests it was off to start with but did you enable it afterwards? Read your phone's display while in download mode for reactivation lock status. If unlocked, the focus should be on flashing the right tar- like the one that matches your data.
Did the downgrade with Odin attempt to flash an older tar not compatible with bootloader? (You can't flash full tars like Android 5.0 or KitKat in Odin).
It may be wise to Odin flash the last stock tar that actually booted and matches your data if you haven't wiped it. Or flash the tar you want- as long as it's allowed- and factory reset in stock recovery and Odin the tar again.
But, if you did enable reactivation lock, you should Odin the full tar that matches your point of lock. You would also need to allow it to auto boot and sign in with same Google user and password.
If still having issues or tried all of that already, I haven't mentioned that you should wipe internal memory with TWRP or CWM. If you've had CM on the phone, you should wipe internal memory before stock tar flash. One thing I prefer to do with stock tars is flash them cleanly: backup first, then wipe everything but extSdCard, power down, pull battery. Wait at least 30 seconds, discharge the power circuit by gently pressing and holding power button with battery removed. Install battery and boot to download mode to flash stock tar with latest Odin and Odin defaults.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
about the factory wipe, i only did the part that i mentioned, those which i didn't mention, no, this is my carelessness
about reactivation lock, i don't really know what is it, is it debugging mode in the developer menu?
the 1st downgrade from 6.0.1 to 5.1.1 both are stock, and is a success, the 2nd downgrade are under the same situation, but failed, when upgrade to 6.0.1, the 1st i use OTA, 2nd i use smart switch, for downgrading in use odin on both, 1st success, 2nd failed, i'm using stock downloaded from sammobile
NooBDroidPlayer said:
about the factory wipe, i only did the part that i mentioned, those which i didn't mention, no, this is my carelessness
about reactivation lock, i don't really know what is it, is it debugging mode in the developer menu?
the 1st downgrade from 6.0.1 to 5.1.1 both are stock, and is a success, the 2nd downgrade are under the same situation, but failed, when upgrade to 6.0.1, the 1st i use OTA, 2nd i use smart switch, for downgrading in use odin on both, 1st success, 2nd failed, i'm using stock downloaded from sammobile
Click to expand...
Click to collapse
The reactivation lock is enabled by two different methods. Manually at Settings/Security; you also get prompted to set it on the last step of setup wizard after flashing a stock tar.
However, you can verify that reactivation lock is off when in download mode. Read your phone's screen. It should say that it is off.
The Note 4 has an infamous tendency to corrupt or just wear out the eMMC due to excessive wipes, format of data and flashes. I would advise limited use of Odin, Smart Switch and OTA updates to minimum to get you where you want to be. Even the multiple use wipes in recovery should be limited. They're all suspect IMO.
Maybe the extra updates you've attempted were due to things not going as expected or you've experienced the failure or corruption of eMMC. I'd suggest you resolve the reactivation lock (If shown to be locked) try the suggested wipe and flash method at end of my first post on the tar you intend to flash to get the ROM of your choice and limit updates as much as possible.
If you get there cleanly with no failure to boot or reboots unexpected reboots thereafter, maybe it was just something that needed clearing out of internal memory. With that in mind, if you get to the point of flashing a custom ROM, read the OP our thread carefully; consider wiping internal memory in custom recovery before flashing ROM, if suggested.
Maybe just format data once per ROM flash. There's also an option in TWRP settings to wipe rather than format.
Sent from my SM-N910P using Tapatalk
Flash Bootloader PG1 and then MIUI 6.6.3 for N910F/G. It should then work
samep said:
The reactivation lock is enabled by two different methods. Manually at Settings/Security; you also get prompted to set it on the last step of setup wizard after flashing a stock tar.
However, you can verify that reactivation lock is off when in download mode. Read your phone's screen. It should say that it is off.
The Note 4 has an infamous tendency to corrupt or just wear out the eMMC due to excessive wipes, format of data and flashes. I would advise limited use of Odin, Smart Switch and OTA updates to minimum to get you where you want to be. Even the multiple use wipes in recovery should be limited. They're all suspect IMO.
Maybe the extra updates you've attempted were due to things not going as expected or you've experienced the failure or corruption of eMMC. I'd suggest you resolve the reactivation lock (If shown to be locked) try the suggested wipe and flash method at end of my first post on the tar you intend to flash to get the ROM of your choice and limit updates as much as possible.
If you get there cleanly with no failure to boot or reboots unexpected reboots thereafter, maybe it was just something that needed clearing out of internal memory. With that in mind, if you get to the point of flashing a custom ROM, read the OP our thread carefully; consider wiping internal memory in custom recovery before flashing ROM, if suggested.
Maybe just format data once per ROM flash. There's also an option in TWRP settings to wipe rather than format.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
i'll be more caution in the future, thank for the great help !!!
I've noticed in my Sprint forum that some users downgrading from Marshmallow to Lollipop with Odin full tar reportedly had to factory reset after Odin of stock Lollipop tar.
They said phone failed to boot until the factory reset.
There's two particulars that apply to quick downgrade in our forum. If you have an old lollipop TWRP backup of desired ROM and an XDA thread that contains bootloader tars to flash in Odin, you can easily just TWRP backup your current Marshmallow ROM, factory reset and wipe internal memory and restore the TWRP backup of Lollipop and Odin the equivalent bootloader. But without the right bootloader, Wi-Fi won't connect and camera won't focus correctly.
You could easily upgrade and downgrade with TWRP backups and bootloader tars that way minimizing excessive wear on eMMC. Just remember to backup current ROM, factory reset, wipe internal memory, restore backup and flash the equivalent bootloader. Keep your backups current and relevant and always backup to ext sdcard- same for titanium backup backups.
Still I prefer to minimize upgrade and downgrade and wipes to possibly extend the life of the eMMC to maximum. I just minimize wipe and flash so much to avoid component wear. Just a theory though. Also try to minimize heat by avoiding fast charging and ventilating phone when optimizing apps on initial boot of new custom ROM or after flashing Xposed or any wipe of dalvik-cache.
Sent from my SM-N910P using Tapatalk
Related
Hi Guys
I am new to playing around with android but not to electronics. I have a Verizon Samsung Galaxy Tab 10.1 16gb (SCH-i905) with current 4g service.
Here is the problem I am having:
It started yesterday, I was browsing the web and the tablet froze and then rebooted. After the reboot programs randomly freeze and crash, if I reboot anything I have downloaded is gone and anything I deleted is back and I can't install or remove apps. I figured I had something corrupted and a factory wipe would fix it. Unfortunately when I perform a factory wipe from the menus or through Android recovery nothing happens. The tablet boots up like nothing was erased. Still has all my accounts, security pin, apps, and so on.
So after that I figured I would flash the tablet, I found the thread here in the development forum with the stock 3.2 image to load through ODIN. I downloaded everything, followed the instructions. ODIN says the flash was successful but when the tablet reboots it still has all my info and is running 4.0.4. I have tried this multiple times. I have tried loading CWM with ODIN but it will not stick.
Any thoughts? If you need more information I will get it, I am just stuck and can't find anything that helps me with this problem!
Thanks for your help!!!
If you want cwm to load after you install it using odin, then you must immediately boot the tablet into recovery without letting it run normally. During the normal boot process, CWM is deleted and the stock recovery is restored. Therefore once Odin finishes installing CWM, hold the volume up button and once you get to the recovery mode you will be running CWM instead of the stock recovery module.
Regards,
Michael
Yes, I did read that in the multiple thread about installing CWM and have gone into recovery directly after ODIN reboots the tablet, however it is still only the stock recovery app.
Any ideas why the factory reset / data wipe won't work?
So after several more hours working on this problem I think I have come across the root cause. I believe that my internal storage has corrupted and is now only mounting in Read-Only mode. From everything I can find online, without having root access previously, this is a no go for fix it yourself.
In case anybody happens on this post down the road, I have been unable to find a resolution and it would appear I must sent the unit back to Samsung for repair.
Mixinitup4Christ said:
So after several more hours working on this problem I think I have come across the root cause. I believe that my internal storage has corrupted and is now only mounting in Read-Only mode. From everything I can find online, without having root access previously, this is a no go for fix it yourself.
In case anybody happens on this post down the road, I have been unable to find a resolution and it would appear I must sent the unit back to Samsung for repair.
Click to expand...
Click to collapse
factory reset through the stock recovery should be able to get you out of it (RO filesystem).
pershoot said:
factory reset through the stock recovery should be able to get you out of it (RO filesystem).
Click to expand...
Click to collapse
I guess that blows my theory out of the water. I can't make heads or tails with this. No matter what I do, Menu Factory Reset, Recovery Wipe/Reset, ODIN Flash Stock EG01 firmware, ODIN flash CWM Recovery as soon as this device reboots I am right back where I started....... GAH!!!
Thanks for letting me know I'm probably wrong.
Mixinitup4Christ said:
I guess that blows my theory out of the water. I can't make heads or tails with this. No matter what I do, Menu Factory Reset, Recovery Wipe/Reset, ODIN Flash Stock EG01 firmware, ODIN flash CWM Recovery as soon as this device reboots I am right back where I started....... GAH!!!
Thanks for letting me know I'm probably wrong.
Click to expand...
Click to collapse
it has to be factory reset through the stock recovery (it will format /data), not through CWM.
rozeins gone
pershoot said:
it has to be factory reset through the stock recovery (it will format /data), not through CWM.
Click to expand...
Click to collapse
Yup, done that multiple times. I'll take video of it if you want, Factory Reset in stock recovery has no effect.
Mixinitup4Christ said:
Yup, done that multiple times. I'll take video of it if you want, Factory Reset in stock recovery has no effect.
Click to expand...
Click to collapse
odin flash CWM (you can use 6.0.2.8 in JB CM10 folder on droidbasement), boot it and try to format the /system partition first then /data.
pershoot said:
odin flash CWM (you can use 6.0.2.8 in JB CM10 folder on droidbasement), boot it and try to format the /system partition first then /data.
Click to expand...
Click to collapse
Will Do, ODIN3 1.85?
pershoot said:
odin flash CWM (you can use 6.0.2.8 in JB CM10 folder on droidbasement), boot it and try to format the /system partition first then /data.
Click to expand...
Click to collapse
HI Pershoot!
I forgot to say thanks for your help!! I appreciate someone smarter than me lending a hand.
That said, I just tried to flash CWM from DB Galaxy Roms/CM10 folder. Upon reboot the tablet still entered stock recovery, I have tried this several times, but this time I took a video. If you feel so inclined to watch it maybe you can catch me doing something wrong....
Again thanks for your help!!
Video of me doing the Stock Recovery Factory Reset
Video of me attempting to flash CWM from droid basement
Mixinitup4Christ said:
HI Pershoot!
I forgot to say thanks for your help!! I appreciate someone smarter than me lending a hand.
That said, I just tried to flash CWM from DB Galaxy Roms/CM10 folder. Upon reboot the tablet still entered stock recovery, I have tried this several times, but this time I took a video. If you feel so inclined to watch it maybe you can catch me doing something wrong....
Again thanks for your help!!
Video of me doing the Stock Recovery Factory Reset
Video of me attempting to flash CWM from droid basement
Click to expand...
Click to collapse
I had to do this on mine. http://techne.alaya.net/?p=8829. I rooted and modified the file described in the steps. Weirdly enough it still booted into stock recovery the first time I installed CWM. I installed CWM one more time and the tablet now boots into CWM.
I have an i9300 international version. It began freezing and boot looping.
Recovery and download mode were working. adb shell was working via recovery.
To figure out why it was bootlooping, I wanted to run adb logcat during boot, but to do this you need to enable usb debugging, and mine was disabled. Obviously I couldn't enable it because I couldn't boot, and even tried to enable via adb shell using the following steps:
/data/data/com.android.providers.settings/databases/settings.db: adb_enabled=1
and
/system/build.prop: persist.service.adb.enable=1
But I couldn't find the above sqlite database. In fact /data was empty and I couldn't access any system files via adb shell anyway.
So no usb debugging, which means the next step is flash a stock rom. I flashed I9300XXEMG4 (here) with Odin, wiped system,data,cache. Still bootlooping (samsung logo - kernel i9300 logo - samasung logo - kernel logo etc).
I read about the PIT file here. I read about how you should stay away from it at all costs. As this was a last ditch attempt I flashed the PIT file GT-I9300_mx_20120329.pit along with I9300XXEMG4.
The phone booted fine!
Unfortunately I just read this post about not coming back from EMG4... and I hadn't backed up the efs partition
Disclaimer: do not flash the PIT file unless you know what the hell you are doing.
P.S. if you have any problems with Odin not working (stuck before it starts flashing), close Odin, unplug USB and take the phone battery out, open Odin, put the battery in, boot into download mode then plug USB in. Worked fine for me.
Cheers
Everytime I flash the stock ROM, I will have bootloop. I get into stock recovery mode, do a factory wipe and reboot. My phone boots up normally after that.
YRAJ23 said:
Everytime I flash the stock ROM, I will have bootloop. I get into stock recovery mode, do a factory wipe and reboot. My phone boots up normally after that.
Click to expand...
Click to collapse
Why are you flashing the stock ROM? Upgrading? If you are flashing a different ROM or different Android version, your /data won't work with the new version. If you are flashing to a similar version, try only wiping the cache and dalvik cache.
thejonesyboy said:
Why are you flashing the stock ROM? Upgrading? If you are flashing a different ROM or different Android version, your /data won't work with the new version. If you are flashing to a similar version, try only wiping the cache and dalvik cache.
Click to expand...
Click to collapse
I'm a flash addict. I will try new ROMs. I case anything went wrong, this will by my rescue step. Last week, my phone's external speaker malfunctioned. So I need to get back to stock. I need to unroot and flash stock firmware. I encountered boothloop. So, do a factory wipe and reboot. All was OK.
YRAJ23 said:
I'm a flash addict. I will try new ROMs. I case anything went wrong, this will by my rescue step. Last week, my phone's external speaker malfunctioned. So I need to get back to stock. I need to unroot and flash stock firmware. I encountered boothloop. So, do a factory wipe and reboot. All was OK.
Click to expand...
Click to collapse
what type of speaker malfunctioning you got? I am facing some problem with audio/video apps. all audio/video related apps(even call ringtones) not running smoothly half of the time. I have tried many roms. Now i flashed stock firmware via odin and still have same issue.
I have not done any data/cache wipe before odin flash. Is full data/cache wipe is required for stock firmware via odin. OR any other solution you can suggest.
siwach said:
what type of speaker malfunctioning you got? I am facing some problem with audio/video apps. all audio/video related apps(even call ringtones) not running smoothly half of the time. I have tried many roms. Now i flashed stock firmware via odin and still have same issue.
I have not done any data/cache wipe before odin flash. Is full data/cache wipe is required for stock firmware via odin. OR any other solution you can suggest.
Click to expand...
Click to collapse
My phone was under warranty. So I reset the binary counter and reflashed stock ROM. Send it to Service Centre. They said my speaker was spoilt. So they replaced the speakers
TLDR; WHENEVER YOU ARE GOING TO FLASH ANYTHING, MAKE REDUNDANT BACKUPS AND GET THEM OFF THE PHONE!
I was on OC and tried a few days ago, running triangle away. It didn't work. I had philz clockwork mod recovery, which worked after flashed with mobile odin pro. Before that, I had twrp latest version.
I accepted the oc ota from nk4, did custom recovery via pc odin, and flashed supersu zip via recovery. Everything pretty much worked. I started getting system process isn't responding dialog during boot. Previously, the only thing that would fix it is boot into recovery and wipe cache. This time, I couldn't even get into custom recovery. I eventually got into a full boot up. I used mobile odin pro to flash the latest twrp recovery and told it to wipe dalvik too. That is what borked my phone. It would reboot then sit at recovery loading screen. I was upset. It would go into download mode but not recovery, and it wouldn't boot. I flashed the latest twrp in pc odin and that didn't help. I flashed nk4 in a couple of later versions of odin and that didn't fix anything. I tried a different usb port on the pc and that didn't help. I wiped cache in nk4 recovery and that didn't help. It would get stuck at yellow sprint boot screen. I knew that if I did a factory wipe in stock recovery that I'd lose all my data on internal storage. I tried many combinations to flash and get things going, to avoid losing data, but it didn't work. I pulled the sd card. Flashed again but that didn't help. I had flashed probably a half dozen times and the phone wouldn't fully boot.
I stumbled into the xda post about a full tar flash for oc. That would take over an hour at my dsl speed. I was getting desparate. I need my old data and a fully working phone for work. I was playing through ideas I'd tell sprint on how I innocently bricked the phone.
I finally pulled the trigger and wiped cache and factory reset 3x each in stock recovery. The phone fully booted. I've spent over two hours trying to get the phone back up via pc odin and titanium backup. I've burned through 90% of a charged battery. I've lost two weeks of personal data I keep track of and can't restore or fix. I'm not a newb.
For crying out loud, before you flash anything, no matter how seemingly insignificant, back up and prepare for any possible losing of all data on the internal memory of the phone!
On android 5.x+, I'm not going to trust anything that flashes that is an app. Triangle away or mobile odin pro!
I will also never take an ota update. I will only trust a full tar.md5 full pc odin flash! Btw, the guy who posted in the full nk4 post, a link to latest odin programs, with odin in the url, my pc antivirus flipped out saying there's a downloader baddie in their odin 3.10 exe.
Been there done that.?
Once you have got working recovery, it automatically enables USB Debugging while on recovery. SO connect your phone at custom recovery to PC with USB cable, get an ADB browser (there are plenty, google! ) run it on PC, and there you have access to your internal storage, copy whatever personal data you have on your internal storage to your PC, after then factory reset.
Moral: Data retrieved from internal storage from non booting phone while on recovery and connected to PC with USB cable.
This is an AT&T Galaxy S4 SGH-I337. The baseband is OC1 and I have Goldeneye51 rom installed with root. I tried wiping the cache. I also tried to downgrade the kernel but I get an error like "check fail: boot" or something like that. All I want is to backup pics and videos from the internal storage before I do a factory reset.
0siribix said:
This is an AT&T Galaxy S4 SGH-I337. The baseband is OC1 and I have Goldeneye51 rom installed with root. I tried wiping the cache. I also tried to downgrade the kernel but I get an error like "check fail: boot" or something like that. All I want is to backup pics and videos from the internal storage before I do a factory reset.
Click to expand...
Click to collapse
Without it booting via (custom - which you obviously don't have, nor can install at this point) recovery or into the OS, you just don't have any options unfortunately. That is, unless you know someone with an NSA type job that has access to tools to read the nand storage directly. Some Galaxy phone developers have made no wipe stock files to restore the phone, but I don't think they have any for the ATT one, though not 100% sure of that. What did you do to mess it up and which bootloader and update were you on to start before installing the rom?
My wife was calling someone. It suddenly froze and rebooted into this bootloop. after a while it gave a message that 'system process is not responding, wait or ok' or something like that. I wiped the cache and now It will show the home screen for a split second, vibrate, then back to the boot logo. I have proper samsung drivers installed but during the bootloop, Device manager only shows 'Samsung Android' and says no driver installed'. IIRC, before rooting and installing GE51, we were on NB1 or NC1 which at the time was the latest stock OTA.
I guess what I was hoping to hear was that I could use adb sideload to install a special apk that would backup/fix something during boot. Thank you very much for the confirmation. I suppose my next step could be to do the factory reset, then dd an image of /data and use data recovery on that image?
A few days ago i got the massage "uid inconsistent feeling lucky" and after a couple of minutes my phone restarted and got stuck on the flashing samsung logo, i was on an official 4.3 rom rooted.
I decided that it's time to move to Lineage OS 7.1.1. I tried to enter twrp recovery that was installed on my device but got stuck on the twrp splash screen and after 2 seconds it reboots the device, i installed 7 different twrp versions 2.8.5.0 - 3.0.2-2 with odin but every time with the same result, stuck on twrp splash screen
So i tried to install a stock rom, after odin finished and the device rebooted it got stuck again on the flashing samsung logo and when i tried to enter the recovery that should be the stock recovery i got an android image with the red triangle and the phone reboots, when i tried to install stock recovery with odin it got stuck on file analysis.
After all that i downloaded cwm recovery and philz recovery and those were the only recovery i can access, i can delete cache and dalvik cache but when i try to wipe data/factory reset when i select the option the phone immediately reboots.
I also tried to install the Lineage OS 7.1.1 official rom with cwm but got an error massage "can't install this package on top of incompatible data. please try another package or run a factory reset".
Please help me
Is the phone encrypted? You confirmed the model # of the phone by booting into download mode?
audit13 said:
Is the phone encrypted? You confirmed the model # of the phone by booting into download mode?
Click to expand...
Click to collapse
The model # GT-I9300 shown in download mode, the phone isn't encryptd
Does the phone reboot when you put it into download mode?
audit13 said:
Does the phone reboot when you put it into download mode?
Click to expand...
Click to collapse
No, download mode works fine
When flashing a stock ROM, Odin gives no errors? Are you able to boot into stock recovery right after flashing a stock ROM?
audit13 said:
When flashing a stock ROM, Odin gives no errors? Are you able to boot into stock recovery right after flashing a stock ROM?
Click to expand...
Click to collapse
No errors in odin, when i try to enter stock recovery after flashing stock rom there is an android picture with red triangle and the phone reboots, the only problem that i had with odin is when i tried to flash only the stock recovery it got stuck on file analysis, in my first post i wrote all the things that i've tried already and what works and doesn't work
I'm at a loss as to what the problem could be. Have you thought about taking the phone to a cell repair shop to see if it can be flashed via JTAG?
audit13 said:
I'm at a loss as to what the problem could be. Have you thought about taking the phone to a cell repair shop to see if it can be flashed via JTAG?
Click to expand...
Click to collapse
this would be my last resort, where i live a shop would charge me more than the phone is worth to repair it, is there a way to factory reset with a software or adb with a phone that can't boot into the os?
The only way I know of is using stock or custom recovery.
audit13 said:
The only way I know of is using stock or custom recovery.
Click to expand...
Click to collapse
can it help if i check the re-partition or erase all nand option in odin?
You need a pit file in order to repartition.
Srgyoel said:
A few days ago i got the massage "uid inconsistent feeling lucky" and after a couple of minutes my phone restarted and got stuck on the flashing samsung logo, i was on an official 4.3 rom rooted.
I decided that it's time to move to Lineage OS 7.1.1. I tried to enter twrp recovery that was installed on my device but got stuck on the twrp splash screen and after 2 seconds it reboots the device, i installed 7 different twrp versions 2.8.5.0 - 3.0.2-2 with odin but every time with the same result, stuck on twrp splash screen
So i tried to install a stock rom, after odin finished and the device rebooted it got stuck again on the flashing samsung logo and when i tried to enter the recovery that should be the stock recovery i got an android image with the red triangle and the phone reboots, when i tried to install stock recovery with odin it got stuck on file analysis.
After all that i downloaded cwm recovery and philz recovery and those were the only recovery i can access, i can delete cache and dalvik cache but when i try to wipe data/factory reset when i select the option the phone immediately reboots.
I also tried to install the Lineage OS 7.1.1 official rom with cwm but got an error massage "can't install this package on top of incompatible data. please try another package or run a factory reset".
Please help me
Click to expand...
Click to collapse
The error you got means you need to wipe the /system partition before you flash Lineage. As for why TWRP isn't working, I'm really not too sure unless the image size is bigger than the actual recovery partition size.
audit13 said:
You need a pit file in order to repartition.
Click to expand...
Click to collapse
The PIT file depends on the phones model or on the rom version or both?
File depends on model number and the amount of internal memory. I think the 9300 has 16 GB.
RealWelder said:
The error you got means you need to wipe the /system partition before you flash Lineage. As for why TWRP isn't working, I'm really not too sure unless the image size is bigger than the actual recovery partition size.
Click to expand...
Click to collapse
the only recovery i can use is cwm or philz, but when i try to wipe data\factory reset the phone reboots right when i select the option and does not complete the wipe\reset, i wiped cache, dalvik cache and system partition, but when i try to install the rom it said incomplete data and i should do a factory reset and i can't do that, i had the latest twrp working before all of this happened
audit13 said:
File depends on model number and the amount of internal memory. I think the 9300 has 16 GB.
Click to expand...
Click to collapse
Thank you, i will try to download the file and re-partition in odin, that is the only thing i haven't tried yet
Is it possible the phone has 32 GB?
audit13 said:
Is it possible the phone has 32 GB?
Click to expand...
Click to collapse
My s3 has 16 gb
Noooo... Dont repartition it. You haven't had anything that says it needs it yet.
Flash the stock firmware twice, back to back then see if you have more control.
If you have a btu device (unlocked international) i can give you my reliable files to flash.
All you'll need for now is the firmware file. Flash it and as the phone reboots (blue pass in odin) you need to get it into download mode again without going to the os, if you miss it just pull the battery and go again.
Once in dl mode for the second time, flash the firmware again. When the phone reboots, before it goes to os, get in into RECOVERY MODE and try to factory wipe it. If successful allow it to reboot again as normal to os.
If the factory wipe fails or the phone still hangs at the samsung logo you have bigger issues.
Beamed in by telepathy.