Database Users

[WIFI Only] [How-to] GT-P1010 Gingerbread Update

I know a lot of people are going to have problems updating to the latest gingerbread build.
PLEASE NOTE: This update will remove root but you can root again with CF-Root from second post.
ALSO, THIS PROCESS WILL WIPE DEVICE!
1) Put your P1010 into download mode (by holding POWER and VOL-DOWN):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2)I went ahead and used ODIN tool to downgrade/upgrade to the latest FROYO firmware before Gingerbread:
P1010XWKC1_OXX
(OEM Flash Guide here)
You should have the same tick marks and files loaded as in my screenshot. Be sure that the box is yellow on the right and you can initiate the firmware install by clicking 'Start'.
3) (VARIES) From there, after restart some people will experience a force close followed by a reboot loop. You will need to flash this kernel via ODIN:
P1010ZHKF1-kernel
(Flash this the same way as above but UNCHECK Re-Partition and CSC!)
4) You will then be able to boot into Froyo.
5) You will use ODIN again to install the Gingerbread update and flash just the PDA (leave CSC blank and leave Re-partition unchecked this time).
P1010XEUKPG
(Flash this the same way you flashed the Kernel in step #2)
6) After it reboots, you will have 2.3.6
7) (Optional) steps in post #2 to install CWM Recovery and Root.

I recommend installing CWM Recovery and CFRoot in the thread below:
ClockWorkMod Recovery for P1010
After you install CWM Recovery, you can do a nandroid backup and never worry about brick again! (=
Also, you can use ES Explorer to mount root and get rid of the Samsung bloatware (AT YOUR OWN RISK!!!)

For those wanting to remove the bloatware (AT YOUR OWN RISK!!!):
You can remove the bloatware with ES Explorer, there's an option to enable 'Root Explorer'. Download the latest version from the Market.
See below:
screenshots are from my Galaxy Nexus but it's the same for any Android 2.2+.
1) Go to the 'Settings' screen
2) Change home directory to '/'
3) Tick the 2 marks on the bottom
4) Browse to /system/app
5) Delete whichever app you don't want, but do it with caution (I usually move these files to /sdcard and move back if it causes any type of force close)
If you totally borked out the system in such a way that you can't boot, you can always move it back in recovery via ADB (much more complicated process but it's possible).
Also, why not do a nandroid backup before messing with deep system files?

Nice! Great topic.

Updated op! =)

this is the best christmas present so far.
edit: worked, almost. thanks ! rooted flashing Skin1980-CF-ROOT-P1010-BETA.tar .
skype isn't using the front camera. =s

Is this for any p1010? Will this work for us models?
Sent from my HTC Flyer P510e using XDA App

r_3 said:
Is this for any p1010? Will this work for us models?
Sent from my HTC Flyer P510e using XDA App
Click to expand...
Click to collapse
It's THE EU ROM but it works with my US P1010.

No restart issues?

r_3 said:
No restart issues?
Click to expand...
Click to collapse
If you followed those steps, the ROM runs stable without any FC's or reboots. I even have setCPU installed on mine.
Also, it's good to note that I'm running CF-Root kernel from the thread in 2nd post.
Plus, you could always downgrade if you run into issues. Just remember to always BACKUP YOUR DATA!

nice!
wow this is good news! does this modded skype work on this: http://forum.xda-developers.com/showpost.php?p=16889575&postcount=1262
or
http://forum.xda-developers.com/showpost.php?p=20697907&postcount=1640
?
I cant try it now as I'm not home. I hope someone could try as so I won't have to think about it until I get home..

@blue_algae: neither the front or the back camera works. tried v11 and v12. so far no luck

densets said:
@blue_algae: neither the front or the back camera works. tried v11 and v12. so far no luck
Click to expand...
Click to collapse
Could you attach the logcat here? or if you could send it directly to theos0o, that'll be great. he's the modder of the skype apps I pasted above.
could you also try this: http://forum.xda-developers.com/showthread.php?t=1153285 this works for me using froyo.

im getting excited about this.. is it really for the p1010 wifi only device? because from what i can see in this subforum is the devs working on the p1000 only. another thing, please don't tell me this is an official update. i don't think the bad sammy will update this little tab.

Depending on where you are freon yes it its the official ireland uk update and makes massive difference as well
Much better tab.
Sent from my GT-P1010 using Tapatalk

skype is working
@densets, skype is working for both skype mods I posted earlier. you just need to enable 'use valid preview'. for droidrx's version, set the app to 'crop' so your video is centered.

phew.. relieved by this news, nevermind if it is not going to be released here in malaysia, at least i can still skype with my family w/o much trouble into getting the ffc to work.

urra901109 said:
phew.. relieved by this news, nevermind if it is not going to be released here in malaysia, at least i can still skype with my family w/o much trouble into getting the ffc to work.
Click to expand...
Click to collapse
hmm, if you are still in froyo, you can use ffc on skype: http://forum.xda-developers.com/showthread.php?t=1153285
just rotate the camera and try out different settings.

sorry for the newbie question, but what's the password for the 2.3.3 file from sammobile?
edit: already found it, my bad

Interestingly, I've followed the guide exactly as mentioned above (had KC1 and the HK kernel from previous flashing) and flashed the PDA for XEU 2.3 from Sammobile, and I'm now stuck in an eternal bootloop. I like the new samsung boot music though, better than the previous one
Any suggestions?
Edit: I wiped data and cache from recovery, flashed KC1 and the Kernel and it boots fine. Checked Kies to be sure and it's offering me FW upgrade to KM2. Should I accept this FW upgrade or just persevere with flashing the new 2.3 firmware?

firmware upgrade encountered an issue! Please help

I know I know there's been quiet a few threads about people screwing up and I'm one of them with a little different problem.
So I really appreciate your help
I have a second I9505 running great on XXUEND1 (almost instant GPS lock) and tried very hard to find this modem to flash on my second I9505 but couldn't find it.
So I thought "lets download the stock which will change the modem, and then restore nandroid" Yes I have a TWRP nandroid I made just before this screw up
So I downloaded this stock from sammobile http://www.sammobile.com/firmwares/download/28734/I9505XXUEND1_I9505TELENC1_TEL
I was on:
GPE 4.4.4
Modem: I9505XXUGNK4
Baseband: I9505XXUGNK4
Loaded the stock firmware in PDA/AP and flashed. FAIL!
Now I can get into download more only (no twrp)
I've attached the screen of Odin 3.09
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How on earth can I flash XXUEND1 and then restore my nandroid???
Cheers guys!

Any help guys? I'm getting nervous here...

The cable should be the stock one and should not be on a hub. Try a different port on the computer, and do not panic. The fact you can get into download mode still means all hope isn't lost.
EDIT: You posted this question twice, with the second location being a development thread, where it really doesn't belong. You received a response there as well: http://forum.xda-developers.com/showpost.php?p=59386461&postcount=18244 . In the future don't cross post, no matter how desparate you are.

Strephon Alkhalikoi said:
The cable should be the stock one and should not be on a hub. Try a different port on the computer, and do not panic. The fact you can get into download mode still means all hope isn't lost.
EDIT: You posted this question twice, with the second location being a development thread, where it really doesn't belong. You received a response there as well: http://forum.xda-developers.com/showpost.php?p=59386461&postcount=18244 . In the future don't cross post, no matter how desparate you are.
Click to expand...
Click to collapse
Thank you, it's directly connected to a port that I've flashed with many times.
I even tried other ports but still same thing.
Did I do wrong by trying to flash the 4.3 from 4.4.4? Or is that asking for trouble?
What else can I do?

sirs2k said:
Thank you, it's directly connected to a port that I've flashed with many times.
I even tried other ports but still same thing.
Did I do wrong by trying to flash the 4.3 from 4.4.4? Or is that asking for trouble?
What else can I do?
Click to expand...
Click to collapse
not sure but it might be partitions (.pit file) - for example one was too short and write failed due to no space left
try flashing the one you were using before (or at least 4.4.2).

Strephon Alkhalikoi said:
The cable should be the stock one and should not be on a hub. Try a different port on the computer, and do not panic. The fact you can get into download mode still means all hope isn't lost.
EDIT: You posted this question twice, with the second location being a development thread, where it really doesn't belong. You received a response there as well: http://forum.xda-developers.com/showpost.php?p=59386461&postcount=18244 . In the future don't cross post, no matter how desparate you are.
Click to expand...
Click to collapse
Yes I'm sorry about that. I was really starting to freak out.
Anyhow, I've managed to flash a 4.4.2 with modem and baseband XXUGNH6. I've also flash the latest twrp. But I would still very much love to complete what I wanted to do in the first place. Which is flashing XXUEND1.
I couldn't find it anywhere as a flashable and I couldn't downgrade to 4.3 which is where it is.
Could you guys please help me get this done?
Cheers

not sure if you have .pit file included in package downloaded form sammobile (the one for 4.3) but if so - add .pit and tick re-partition, while flashing 4.3 as you tried before.
re-partition, if it will include data partition will erease all your data - backup your movies, photos, etc before proceeding.
Sent from my TF300T using XDA Free mobile app

th3cr0w said:
not sure if you have .pit file included in package downloaded form sammobile (the one for 4.3) but if so - add .pit and tick re-partition, while flashing 4.3 as you tried before.
re-partition, if it will include data partition will erease all your data - backup your movies, photos, etc before proceeding.
Sent from my TF300T using XDA Free mobile app
Click to expand...
Click to collapse
Thanks mate,
Just managed to get it back to normal bu flashing 4.2.2, then downgraded to 4.3 XXUEND1.
Now the build is showing as XXUEND1. However the bootloader and baseband stayed at XXUGNH6!
IS it possible to flash XXUEND1 modem/baseband on this now?
I've tried compiling the modem flashable but aren't savvy enough! So here are the files if it's possible to flash
Modem: https://mega.co.nz/#!HRNHQZob!WLfbPp...ZHF7pAd5HmC00U
NON-HLOS: https://mega.co.nz/#!iVFjWCZI!jcUyjN...WP8kfnQZbIxDi0
Really appreciate your help!

sirs2k said:
Thanks mate,
Just managed to get it back to normal bu flashing 4.2.2, then downgraded to 4.3 XXUEND1.
Now the build is showing as XXUEND1. However the bootloader and baseband stayed at XXUGNH6!
IS it possible to flash XXUEND1 modem/baseband on this now?
I've tried compiling the modem flashable but aren't savvy enough! So here are the files if it's possible to flash
Modem: https://mega.co.nz/#!HRNHQZob!WLfbPp...ZHF7pAd5HmC00U
NON-HLOS: https://mega.co.nz/#!iVFjWCZI!jcUyjN...WP8kfnQZbIxDi0
Really appreciate your help!
Click to expand...
Click to collapse
Those links ask for password - not sure what would that be
You can always extract modem and non-hlos form your XXUEND1 package downloaded from sammobile and flash them separately via Odin as in here:
http://forum.xda-developers.com/gal...o-flash-modems-baseband-t3028314/post58785261

[Q] Flashing 4.4.2, or Custom ROM?

Hey Y'all,
So I've been trying to root my 5.0.1 S4, but could not do it for the life of me. I figured since the CF Auto Root file was made for 4.4.2, I would try flashing back to that with Odin. After getting the correct build for my device, I've been trying to get it to flash, but it got to system, and then stalled forever. I let it run overnight, and it hadn't progressed, so I tried restarting. Now, it fails in a matter of seconds, but I keep seeing progress on the phone's blue bar.
[Q] AM I wasting my time trying to flash an old build? If so, should I just use a custom rom so I get my root? And if so, which one should I use (I'm new to this phone mod stuff.)
Thanks in advance!

F13Bubba said:
Hey Y'all,
So I've been trying to root my 5.0.1 S4, but could not do it for the life of me. I figured since the CF Auto Root file was made for 4.4.2, I would try flashing back to that with Odin. After getting the correct build for my device, I've been trying to get it to flash, but it got to system, and then stalled forever. I let it run overnight, and it hadn't progressed, so I tried restarting. Now, it fails in a matter of seconds, but I keep seeing progress on the phone's blue bar.
[Q] AM I wasting my time trying to flash an old build? If so, should I just use a custom rom so I get my root? And if so, which one should I use (I'm new to this phone mod stuff.)
Thanks in advance!
Click to expand...
Click to collapse
Yes, stop before you brick your device. CF Auto Root works for Lollipop. Or Odin TWRP and flash SuperSU zip. Or just flash a rooted ROM. Read the OPs and decide which one sounds like the best fit for you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

bilgerryan said:
Yes, stop before you brick your device. CF Auto Root works for Lollipop. Or Odin TWRP and flash SuperSU zip. Or just flash a rooted ROM. Read the OPs and decide which one sounds like the best fit for you.
Click to expand...
Click to collapse
KK, thanks. I could not get CF to root my device, trying 3 different versions of Odin. I'll go the custom rom route, methinks.

F13Bubba said:
KK, thanks. I could not get CF to root my device, trying 3 different versions of Odin. I'll go the custom rom route, methinks.
Click to expand...
Click to collapse
Uncheck Auto Reboot and F Reset (everything) when using Odin. And wait a minute after it says PASS before unplugging. Also try different ports and cables.

I can only find .img files for TWRP, I haven't yet been able to find any .tar files. Any tips on where to get a recovery file to use with Odin?
Yeah, definitely cannot restart my phone at the point, it's referring me to Kies to recover. Kies won't connect, either 3.0 or 2.6. So At this point I guess I'm hoping flashing a custom ROM will work...otherwise, is my phone bricked?

F13Bubba said:
I can only find .img files for TWRP, I haven't yet been able to find any .tar files. Any tips on where to get a recovery file to use with Odin?
Yeah, definitely cannot restart my phone at the point, it's referring me to Kies to recover. Kies won't connect, either 3.0 or 2.6. So At this point I guess I'm hoping flashing a custom ROM will work...otherwise, is my phone bricked?
Click to expand...
Click to collapse
TWRP can flash images now.
Flash this build of TWRP first. (It's a .tar for Odin)
https://dl.twrp.me/jfltespr/twrp-2.8.4.0-jfltespr.tar
Copy this build to your device somewhere. (You might as well go ahead and copy a ROM you want to install on your device also.)
https://dl.twrp.me/jfltespr/twrp-2.8.7.0-jfltespr.img
Boot into TWRP and go to install. Select images button at the bottom right and select the build you copied to your device. You will now be running the current version of TWRP.

WOOOOOO!
After a ton of troubleshooting and grief, I finally got 5.0.1 back on, and working. I also discovered that my front usb port was not working correctly. I guess I'll try to root it now!
Aaaaaand, it seems to have worked flawlessly. Thanks for all the help guys!

Phone crashes on boot - even flashed new stock rom

I have a spare galaxy s5 at home that I would like to get up and going, it's kltedv. Every time it boots the phone restarts and gives android crash errors. I've flashed stock onto it and it still does the same thing. Is there a way to rebuild everything using Odin that may fix it?
Sent from my SM-G900I using Tapatalk

chainzy said:
I have a spare galaxy s5 at home that I would like to get up and going, it's kltedv. Every time it boots the phone restarts and gives android crash errors. I've flashed stock onto it and it still does the same thing. Is there a way to rebuild everything using Odin that may fix it?
Sent from my SM-G900I using Tapatalk
Click to expand...
Click to collapse
Sounds like you didn't factory reset your device. Before you factory reset, I recommend flashing TWRP recovery, mount your phone in recovery so you can back up important files to your PC if required.
After you've backed-up your files
Reboot (yes reboot, so switch your device off first) into the recovery menu (hold vol up + home + power), then select wipe data. This will wipe all data from your phone.

chainzy said:
I have a spare galaxy s5 at home that I would like to get up and going, it's kltedv. Every time it boots the phone restarts and gives android crash errors. I've flashed stock onto it and it still does the same thing. Is there a way to rebuild everything using Odin that may fix it?
Sent from my SM-G900I using Tapatalk
Click to expand...
Click to collapse
Where you cumming frop lolipop rom and flashed marshmallow or nougat rom ? If yes have you tick bootloader update in odin ? Rom will never boot without this update ! Try this if the previous good advice from Saber didn't help .

Everything is wiped. This is what happens when booting. Lines going across the screen. What originally happened was the person I got it from he had tried to do a update and the phone turned off. So I just flashed stock firmware but still get these lines.. Something is corrupted?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-G900I using Tapatalk

When it boots in everything crashes in setup, get the error message unfortunately has stopped
Sent from my SM-G900I using Tapatalk

Looks like your phone needs a new main logic board because of defective memory.

chainzy said:
When it boots in everything crashes in setup, get the error message unfortunately has stopped
Click to expand...
Click to collapse
Here's my two cents if you've done what @Saber and @1981sebas suggested and still had no luck.
First, make sure the stock you've flashed is the latest MM XSA version to ensure you have the latest bootloader and modem. You can get it from sammobile or updato. It may take a couple of attempts so don't panic if it doesn't stick first time.
If it's still not right, hunt up the PIT files for your device and repartition it. Make sure you get legit files that others have used and had success with. You don't want to flash the wrong PIT. Then try flashing stock again.
Incidentally, have you tried flashing a solid custom ROM like RR or Cosmic? Maybe it's just an issue with your stock file being a bit corrupt if you haven't checked the md5 and any intact ROM will work fine.
My last option would be to try KIES because I personally find it iffy but others have had success with the recover phone option or whatever it's called. If you have KIES installed, just make sure it's disabled when you're using Odin and vice versa.
If none of this works, it may be a hardware issue. Good luck.
Sent from my Samsung SM-G900I using XDA Labs

I have tried a pit file I have but it didn't seem to do anything with that and re partition checked. I have tried several stock roms. Even tried the firmware with kies and still the same thing happens. Custom rom does the same.. The lines only come up on the screen when its booting.. They never come up in recovery or anything like that
Sent from my SM-G900I using Tapatalk

Dirty Flasher said:
hunt up the PIT files for your device and repartition it
Click to expand...
Click to collapse
That may be the case.
I'd try to download the latest "low_ship" factory firmware via Samfirm.
It contains a proper pit file in the CSC so it's necessary simply to flash it via Odin to repartition the device and clean everything on it.

I bricked my phone [Samsung A40]

Hello guys,
I have tried several wrong root firmwares for my SM-A405FN smartphone. I thought it was A30 so I tried flashing custom roms for A30.
And I got "This phone is not running Samsung's official" error which it loops and enter in download mode everytime.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
then I flashed the WRONG stock rom for A30, despicte the fact I have A40.
The problem here, was that I couldn't flash anything due to some misterious "could not connect error".
After that appeared on the screen some information about the PIT,on the download mode.
I tried also flashing the firmware for the PIT, which it actual repartions the phone, and it runned succesefully. But I ended with this error:
"Error validating footer (6)
..tom recovery
Meta a405fnxxu4cv62, 54217902R"
My question it's if you know how to recuperate back my phone?
Next, I'm gonna try flashing my stock rom, preferably for Ver 9.0 / Pie Version. Then working on a solution for the problem above. And after that how to bypassing "Not running official Samsung".

Cristishor201 said:
....
I tried also flashing the firmware for the PIT,......
Click to expand...
Click to collapse
at 1st I don't own that device but several other Samsungs
Which FW was that? the right one?
Where from did you get it?
Do you have multiple part stock ROM (AP, BL, CSC, CP all as separate files)?
Download mode still working?
Odin still recognises the phone?
Flashing the firmware for pit doesn't work to repartition it.
Pit file has to be extracted from CSC file and placed in Odin separatly and "repartion" box checked.

UPDATE1:
I tried to upload stock with Odin, but I encountered an error.
Then I restarted the phone, and I got this message:
And I found on youtube & here on xda, that I have to use Smart Switch, old version.
Now I can not find the Serial Number, on the box... and I might have to uncover the back of the phone.

@Cristishor201 to me it seems there is no (stable) usb connection if at all.
Doesn't COM field in Odin turn blue when you connect it to PC?
Tried other cables or USB ports?
Btw to let me get a notification put a @ before my name

bmwdroid said:
at 1st I don't own that device but several other Samsungs
Which FW was that? the right one?
Where from did you get it?
Do you have multiple part stock ROM (AP, BL, CSC, CP all as separate files)?
Download mode still working?
Odin still recognises the phone?
Flashing the firmware for pit doesn't work to repartition it.
Pit file has to be extracted from CSC file and placed in Odin separatly and "repartion" box checked.
Click to expand...
Click to collapse
@bmwdroid:
1. I didn't used the right FirmWare from the begining. I used recovery for A30 instead A40
2. I got the stock from updato.com
3. yes, I do. I even have an CSC and a CSC_HOME
4. now download mode is no longer working...
5. yes, Odin still recognise the phone.
bmwdroid said:
@Cristishor201 to me it seems there is no (stable) usb connection if at all.
Doesn't COM field in Odin turn blue when you connect it to PC?
Tried other cables or USB ports?
Btw to let me get a notification put a @ before my name
Click to expand...
Click to collapse
6. Yes, it turns blue and it says COM8.
7. Only his cable. Is the only one C type cable.
do you think that I shall find the serial number on the back of plastic inside phone ? or do you know a work around without serial number ?

Cristishor201 said:
@bmwdroid:
1. I didn't used the right FirmWare.....
Click to expand...
Click to collapse
I understood that
Cristishor201 said:
... I used recovery for A30 instead A40
Click to expand...
Click to collapse
You mean TWRP? I thought you've flashed wrong firmware not wrong recovery.
Cristishor201 said:
2. I got the stock from updato.com
Click to expand...
Click to collapse
Solid source although I prefer SamFirm_Reborn_0.3.6.3
Cristishor201 said:
3. yes, I do. I even have an CSC and a CSC_HOME
Click to expand...
Click to collapse
Use CSC only for now, HOME only for keeping data when updating the correct firmware
Cristishor201 said:
4. now download mode is no longer working...
5. yes, Odin still recognise the phone.
6. Yes, it turns blue and it says COM8.
Click to expand...
Click to collapse
Download mode gotta be working when Odin recognises the phone.
I think you mean something else.
Cristishor201 said:
7. Only his cable. Is the only one C type cable.
do you think that I shall find the serial number on the back of plastic inside phone ? or do you know a work around without serial number ?
Click to expand...
Click to collapse
I've no idea. It former times the numbers where there.
If you haven't kept the box, no. But what will the number be good for?
On my other Samsungs with not detachable batteries it's printed on the back although very hard to read.

Double post

bmwdroid said:
If you haven't kept the box, no. But what will the number be good for?
Click to expand...
Click to collapse
At using Smart Switch, it asks me for the model, and serial number

sebbialsvikk said:
I found a way you wouldn't expect. Run odin, flash a recovery, flash stock rom, and you good to go. Odin acctually find the device. .
Click to expand...
Click to collapse
I was able to return to Download mode, by flashing the twrp (the right one).
But it still fails..

@bmwdroid​After I changed the cable, and flashed the latest stock (EMUI 11, instead EMUI 9), I did pass that error, and get repaired.
It get started with the initial installation steps.