Related
Hello everyone!
I've proved a pride name of noob in Android by flashing ebtblob.bin for TF201 downloaded @ here _ttp://androidroot.mobi/t3_nvflash/.
Now it's flashing and cannot start even to show a single icon at screen, and I can't turn it off.
But I can enter fastboot mode.
What could I do right now?
P.S. fastboot devices reports now
00000 fastboot
Click to expand...
Click to collapse
instead of
???????????? fastboot
Click to expand...
Click to collapse
Dun brick'd.
Sent from my PG86100 using Tapatalk 2
If you really can enter fastboot, you should be able to flash a stock image blob.
Download the appropriate firmware from ASUS (http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download). Inside the zip you get is another zip, and inside that other zip there's a file named 'blob'. Extract that file and the run 'fastboot flash staging blob' (where blob is your newly extracted file) and then 'fastboot reboot'. You may need to run fastboot with that '-[something] 0x[something]' argument for it to work.
If fastboot really does still work, that should bring you back to the stock bootloader. Good luck!
Also, don't attempt to use that nvflash kit again. It's ONLY for TF201 right now.
Keion said:
Dun brick'd.
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
What are you trying to prove with these "helpful" posts everywhere? Or is needling people just your way of amusing yourself out of boredom while downloading the anime? I did not enjoy the earlier "he's a troll" show, but I think I'll change my mind on this. Look at the following post for reference on how this forum should work.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Dun brick'd.
Click to expand...
Click to collapse
Thanks, very informative.
firetech, thank you! I;m trying the third time... Seems that it has not eventually rejected the file.
For a couple of times it happened so:
sudo /opt/android-sdk/platform-tools/fastboot -i 0x0b05 flash staging ebtblob.bin
sending 'staging' (998 KB)...
FAILED (remote: (AccessDenied))
finished. total time: 0.030s
Click to expand...
Click to collapse
But now it's doing something %)
for 1. this thread does not belong in development. please read the rules about posting. This thread has nothing to do with development therefore does not belong here. 2. OP you should really learn more before doing this type of stuff. I mean flashing something that is for a different device? You should have known better and if you didnt know better in all due respect should stay away from flashing completely until you read, read and read some more and grasp everything
Thread moved to correct board..
NetBUG said:
firetech, thank you! I;m trying the third time... Seems that it has not eventually rejected the file.
For a couple of times it happened so:
But now it's doing something %)
Click to expand...
Click to collapse
You should NOT try to flash that 'ebtblob.bin' file from AndroidRoot on your TF700 again! It's ONLY made for the TF201! What I told you to flash was the 'blob' file from a stock firmware download... Or did you overwrite your old 'ebtblob.bin' with the stock 'blob' file?
graffixnyc said:
for 1. this thread does not belong in development. please read the rules about posting. This thread has nothing to do with development therefore does not belong here. 2. OP you should really learn more before doing this type of stuff. I mean flashing something that is for a different device? You should have known better and if you didnt know better in all due respect should stay away from flashing completely until you read, read and read some more and grasp everything
Click to expand...
Click to collapse
I see, sorry, but still.
I replaced the staging with ebtblob.bin for TF201, yeah, and got black screen.
Now I reflashed it with blob from original picture and got image and some kind of loading. Hope to recover soon.
P.S. fastboot mode takes HUGE time to flash, I spent over 4 hours and finally the device went down due to discharging.
Thanks anyone for help and now we know that devices can be recovered if flashed wrong, although VERY slowly.
Reflashing it WITHOUT AC power nearby? You're really trying to kill this tablet, aren't you?
Einride said:
Reflashing it WITHOUT AC power nearby? You're really trying to kill this tablet, aren't you?
Click to expand...
Click to collapse
If I can make it there, I'll make it anywhere, it's up to you...
(suddenly started playing in my head ;>)
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Einride said:
Reflashing it WITHOUT AC power nearby? You're really trying to kill this tablet, aren't you?
Click to expand...
Click to collapse
How would you do fastboot on this tablet WITH AC power supply? There is only one USB/charging port, and it doesn't get charged over USB only...
Do a full charge first, I guess. But perhaps it would be easier to flash the recovery through ADB and go from there?
Einride said:
Reflashing it WITHOUT AC power nearby? You're really trying to kill this tablet, aren't you?
Click to expand...
Click to collapse
I had AC power nearby, but how could I use? Disconnect from USB during reflash?
It took about 5 hours before it died.
The best is that it finally, works.
Thanks all, I've found a proper guide to load custom ROMs.
firetech said:
How would you do fastboot on this tablet WITH AC power supply? There is only one USB/charging port, and it doesn't get charged over USB only...
Click to expand...
Click to collapse
..umm reading these posts ,,,> and ....suddenly ... "" DOH "" keeps repeating on brain ,,,,,,, grrr..
>>am jelious mr Firetech .... last time I was in Lund =you live in amazin part of this earth ,,,,,,,,, very fond memories of many a trip to MalMo.....and across bay to Copenhagen.... and often drivein trip north past Helsingborg , Lund etc ,,, ohh those were the endless spring & summer days ....
Cheers!
d14b0ll0s said:
Do a full charge first, I guess. But perhaps it would be easier to flash the recovery through ADB and go from there?
Click to expand...
Click to collapse
It did not work at ADB mode. Actually, i had the black screen, and the backlight was flashing once per three seconds, that I had.
Now I've installed TWRP and everything seems much better.
I'm too much used to WM-based devices with direct reflash
P.S. Surely, I'd never begin to flash a not fully charged device.
P.P.S. Since my TF700 works now, I think the main topic can be closed and the solution, though a bit ramshackle, put info Wiki:
Never flash any file intended for another device, unless the compatibility is proved
The device can be repaired by means of flashing the blob of the same firmware via fastboot mode
Fastboot mode is very slow, so a full firmware (~800 Mb) can't be flashed during a single charge
I see Glad you're back on, I learned my lessons after softbricking mine some time ago.
So what do you mean by the same firmware? (point 2.)
NetBUG said:
I had AC power nearby, but how could I use? Disconnect from USB during reflash?
It took about 5 hours before it died.
The best is that it finally, works.
Thanks all, I've found a proper guide to load custom ROMs.
Click to expand...
Click to collapse
Yeah, I wasn't thinking clearly either. Sorry for that "outburst"
Glad you got it up and running again. Makes for a good learning experience (and teaching us I guess), doesn't it?
d14b0ll0s said:
So what do you mean by the same firmware? (point 2.)
Click to expand...
Click to collapse
Well, as it's clear that fastboot does not allow to reflash full ROM for a single charge and since it writes block-by-block, not in file-based mode, we can get something broken if the firmware differs.
Ex., I had 9.4.5.26 firmware, if I flashed 9.4.5.22 and the tablet dies when it's rewriting blocks that differ in there firmwares, I'd get some software broken (and FS errors).
When reflashing the same (9.4.5.26) firmware I've much more probability that the blocks under system files will be the same, and as I have all firmware except bootloader working, I don't need to perform a full reflash, so the tablet could die any time after the proper bootloader has been uploaded.
Surely, even if firmware differs, I can always reflash it in adb mobe after the bootloader is fixed and the device perfoms initial boot steps without errors, but it adds one more step.
That's perfectly understandable, but the way it was put in context in your post it could suggest you meant to flash the same blob from another device that got you into trouble in the first place, which was rather surprising
Ok so i was on my phone when all of a sudden my home screen kept crashing and pushing the window to close it. So i closed it and powered down the phone thinking a restart would help. It subsequently went to the Encryption Unsuccessful page where it tells you that your phone will need a Factory Reset. So i power down my phone and some times itll restart to the "E.U" screen 3/4 times. When i get it to power down and not power on i try to use the Volume+&Power. It'll pull to the menu and ill scroll to the Recovery and click it but itll push right back to the " Encryption Unsuccessful" screen. On the "Encryption Unsuccessful" Page i have a "Reset Phone" button but it does nothing but turn blue from gray when i press it. I can even take screenshots on the "E.U" page. I URGENTLY need my phone because im constantly awaiting interview calls and im waiting for a certain one. Will try other things until i get a Reply from this. If I fix it over night (well morning now) ill let you know with what stwps
sorry bout your troubles man, bad timing....i dont have a Max and I dont encrypt my phone. Are you on stock ROM? what version?
You most likely will need to flash with rsd lite, a stock rom then go from there
hbenz2008 said:
sorry bout your troubles man, bad timing....i dont have a Max and I dont encrypt my phone. Are you on stock ROM? what version?
You most likely will need to flash with rsd lite, a stock rom then go from there
Click to expand...
Click to collapse
I was on the most updated STOCK ROM. And i didnt want to encrypt my phone either i think i may have hit that setting when my homescreen was crashing over and over. I was wondering if it could be heat damage because I have a laptop with a metal case (****ing Dumbass Alienware) and i was playing rust for almost the whole day and it gets like hot to the touch when i play that long and the phone was in my pocket. If you could link me to a tut for how to flash with rsd and a link to the stock ROM ill go through and try that tonight and post my results either in the am or right when i finish depending on what time it is and what im doing.
Another thing that sucks is theres no warranty and i have no carrier on it ATM (its a verizon phone without the sim, basically an android ipod)
Rsd lite 6.1.6:
http://forum.xda-developers.com/showthread.php?t=2637338
Moto firmware:
http://sbf.droid-developers.org/
How to:
http://www.howardforums.com/showthr...ellyBean-on-PagePlus-VOICE-SMS-MMS-3G-WORKING
KingHephaestus said:
I was on the most updated STOCK ROM. And i didnt want to encrypt my phone either i think i may have hit that setting when my homescreen was crashing over and over. I was wondering if it could be heat damage because I have a laptop with a metal case (****ing Dumbass Alienware) and i was playing rust for almost the whole day and it gets like hot to the touch when i play that long and the phone was in my pocket. If you could link me to a tut for how to flash with rsd and a link to the stock ROM ill go through and try that tonight and post my results either in the am or right when i finish depending on what time it is and what im doing.
Another thing that sucks is theres no warranty and i have no carrier on it ATM (its a verizon phone without the sim, basically an android ipod)
Click to expand...
Click to collapse
its possible rsd may work, but i wouldnt be surprised if it doesnt. encryption errors are bad and sometimes unfixable.
if you are able to boot the phone and tell me the system version, i can provide an end all script to try.
if you cant get the system version, have you taken an update in the last couple weeks? that will tell me what you are on if yes or no.
also, you will need to be able to get into fastboot to use any script, you can get there right?
Encryption errors are triggered by the data partition becoming unmountable (data file system corruption?).
Data and data/media wipe (factory reset) could fix it (unless the data partition part of storage device is physically damaged).
hbenz2008 said:
Rsd lite 6.1.6:
http://forum.xda-developers.com/showthread.php?t=2637338
Moto firmware:
http://sbf.droid-developers.org/
How to:
http://www.howardforums.com/showthr...ellyBean-on-PagePlus-VOICE-SMS-MMS-3G-WORKING
Click to expand...
Click to collapse
Thank you for providing the link to everything i will be trying that in the morning just to give it a try
bweN diorD said:
its possible rsd may work, but i wouldnt be surprised if it doesnt. encryption errors are bad and sometimes unfixable.
if you are able to boot the phone and tell me the system version, i can provide an end all script to try.
if you cant get the system version, have you taken an update in the last couple weeks? that will tell me what you are on if yes or no.
also, you will need to be able to get into fastboot to use any script, you can get there right?
Click to expand...
Click to collapse
No i hadn't updated it in the past weeks and yes i can get into fastboot.
kabaldan said:
Encryption errors are triggered by the data partition becoming unmountable (data file system corruption?).
Data and data/media wipe (factory reset) could fix it (unless the data partition part of storage device is physically damaged).
Click to expand...
Click to collapse
Yeah i believe it may of been heat damage because of my laptop accumulating a lot of heat on the metal casing and that combined with 17hrs of Archeage = one hot laptop
And also for all who replied i sometimes get a picture of the little android dude laying down with his stomach hatch open and a caution sybol above it. Dont know if thats something bad or if its just buggy because i can hard reset it (pwr + Vol-) and turn it back to the encryption unsucsessful page.
KingHephaestus said:
Thank you for providing the link to everything i will be trying that in the morning just to give it a try
No i hadn't updated it in the past weeks and yes i can get into fastboot.
Yeah i believe it may of been heat damage because of my laptop accumulating a lot of heat on the metal casing and that combined with 17hrs of Archeage = one hot laptop
And also for all who replied i sometimes get a picture of the little android dude laying down with his stomach hatch open and a caution sybol above it. Dont know if thats something bad or if its just buggy because i can hard reset it (pwr + Vol-) and turn it back to the encryption unsucsessful page.
Click to expand...
Click to collapse
regardless of the issue, "if it is fixable", this will do it.
there are certain situations that cant be fixed by rsd and standard fastboot. the above tool will fix any issue that is fixable.
bweN diorD said:
regardless of the issue, "if it is fixable", this will do it.
there are certain situations that cant be fixed by rsd and standard fastboot. the above tool will fix any issue that is fixable.
Click to expand...
Click to collapse
sorry i havent replied in a few days life got in the way. But i will finally be trying the rsd and fastboot fix today and to the person who posted the rar can you tell me what im supposed to do with that? Youre hand a laptop guy a bunch of phone programs without instructions.
My device is OnePlus 8 IN2010, but currently I'm on OOS13-F15 IN2015. Everything was working fine without any issues. Last Sunday, I found link to a full ROM F15 of EU variant, then I extract the ops file into fastboot images and flash to the device. The flashing was successfully without any error msg. But then, wen reboot, the device won't turn on again till now. I tried many way but its even not recognized by Computer, no port, no EDL nothing at all.
So I really need if anyone used to face this situation pls share the information on why is it so and is there any solution for the current state of the device.
Thanks in advance, guys!
LinhBT said:
My device is OnePlus 8 IN2010, but currently I'm on OOS13-F15 IN2015. Everything was working fine without any issues. Last Sunday, I found link to a full ROM F15 of EU variant, then I extract the ops file into fastboot images and flash to the device. The flashing was successfully without any error msg. But then, wen reboot, the device won't turn on again till now. I tried many way but its even not recognized by Computer, no port, no EDL nothing at all.
So I really need if anyone used to face this situation pls share the information on why is it so and is there any solution for the current state of the device.
Thanks in advance, guys!
Click to expand...
Click to collapse
It takes several tries while using different ports and cables.
Spoiler
Press and Hold Power Off and Volume Up button and release when the screen goes off. Now your phone is switched off. Now to enter the EDL mode you need to press and hold volume up and volume down buttons at the same time...and then connect the mobile to Windows while still holding the buttons. Done. MSM tool will detect your phone.
rodken said:
It takes several tries while using different ports and cables.
Spoiler
Press and Hold Power Off and Volume Up button and release when the screen goes off. Now your phone is switched off. Now to enter the EDL mode you need to press and hold volume up and volume down buttons at the same time...and then connect the mobile to Windows while still holding the buttons. Done. MSM tool will detect your phone.
Click to expand...
Click to collapse
I did bro, tried not only few times but whole night ))) Besides, tricks like press and hold ( and keep holding ) 3 buttons and else I also did try. I even open the back cover, but not yet know where's the Testpoin
LinhBT said:
I did bro, tried not only few times but whole night ))) Besides, tricks like press and hold ( and keep holding ) 3 buttons and else I also did try. I even open the back cover, but not yet know where's the Testpoin
Click to expand...
Click to collapse
It seems that your device is a candidate for a replacement if you cannot enter EDL.
rodken said:
It seems that your device is a candidate for a replacement if you cannot enter EDL.
Click to expand...
Click to collapse
In fact I considered its ded already, too. Since I unbricked many kind of devices and when I see its state, I already guessed. But what I wanna know is the reason that make him dead bro
LinhBT said:
In fact I considered its ded already, too. Since I unbricked many kind of devices and when I see its state, I already guessed. But what I wanna know is the reason that make him dead bro
Click to expand...
Click to collapse
Something along the way when you flashed the ops file that set the voltage too high on LPDDR5 which might have caused the official bootloader to kill the motherboard beyond MSM.
OnePlus uses same signature to sign all four firmwares, OP8, OP8T, OP8Pro, 9R all use identical signature, which means that PBL (Primary Bootloader) will load XBL (Secondary Bootloader) no matter which one you choose to flash.
Arguably, the reason why the phone died is because LPDDR5 RAM uses lower voltage compared to LPDDR4X, and just because there's no code to prevent XBL from setting voltage too high on LPDDR5, it leads to RAM getting overvolted and dying.
rodken said:
Something along the way when you flashed the ops file that set the voltage too high on LPDDR5 which might have caused the official bootloader to kill the motherboard beyond MSM.
OnePlus uses same signature to sign all four firmwares, OP8, OP8T, OP8Pro, 9R all use identical signature, which means that PBL (Primary Bootloader) will load XBL (Secondary Bootloader) no matter which one you choose to flash.
Arguably, the reason why the phone died is because LPDDR5 RAM uses lower voltage compared to LPDDR4X, and just because there's no code to prevent XBL from setting voltage too high on LPDDR5, it leads to RAM getting overvolted and dying.
Click to expand...
Click to collapse
This I know, but it applies for 8T more than OP8 since op8 only have one LPDDR4 variant, and also in the ops extracted image, there was only 1 xbl and xbl_config image, none xbl5. Thats why I feel weird.
You're looks like Chinese and I'm pretty sure you're. Why not you just make a call to service center or bring to him and they'll fix it in minutes.
Even you can help us for remote season.
By the way op8 have way bh force goto edl
rodken said:
Something along the way when you flashed the ops file that set the voltage too high on LPDDR5 which might have caused the official bootloader to kill the motherboard beyond MSM.
OnePlus uses same signature to sign all four firmwares, OP8, OP8T, OP8Pro, 9R all use identical signature, which means that PBL (Primary Bootloader) will load XBL (Secondary Bootloader) no matter which one you choose to flash.
Arguably, the reason why the phone died is because LPDDR5 RAM uses lower voltage compared to LPDDR4X, and just because there's no code to prevent XBL from setting voltage too high on LPDDR5, it leads to RAM getting overvolted and dying.
Click to expand...
Click to collapse
Besides, I manually flashed it using fastboot cmd-line, not using MSM. So strange!
LinhBT said:
Besides, I manually flashed it using fastboot cmd-line, not using MSM. So strange!
Click to expand...
Click to collapse
At this point and juncture, it wouldn't matter which method was used to flash the ops file. Something along the way set the voltage too high which possibly damaged the motherboard.
Daniha said:
You're looks like Chinese and I'm pretty sure you're. Why not you just make a call to service center or bring to him and they'll fix it in minutes.
Even you can help us for remote season.
By the way op8 have way bh force goto edl
Click to expand...
Click to collapse
1stly, I MAY look like Chinese since we both Asian, but as in my profile is clarify enough that I'm Vietnamese. Besides, it does not related to the issue that I'm raising.
rodken said:
At this point and juncture, it wouldn't matter which method was used to flash the ops file. Something along the way set the voltage too high which possibly damaged the motherboard.
Click to expand...
Click to collapse
Basically, its the only way for now to explain the situation, but to be honest, Im not so satisfy with it. Point is, I'm not trying to recover the device for myself since personally, I considered its ded ))). But also I want to help all the information which may related to the issue, from there I will have clues to find out what was the reasons that killed it, then share to the community to prevent the same issues since even that Im quite experienced with OP devices but this is the 1st time I face this so it may be the new issue which comes with OOS13 or else.
LinhBT said:
1stly, I MAY look like Chinese since we both Asian, but as in my profile is clarify enough that I'm Vietnamese. Besides, it does not related to the issue that I'm raising.
Click to expand...
Click to collapse
You stil missed My POV. You need to visit service Center the only option left in this case. I can also fix but device need in hand.
Here everyone Provide you file but what if you're Not able to access 9008
Or another option is ufs dump
LinhBT said:
Basically, its the only way for now to explain the situation, but to be honest, Im not so satisfy with it. Point is, I'm not trying to recover the device for myself since personally, I considered its ded ))). But also I want to help all the information which may related to the issue, from there I will have clues to find out what was the reasons that killed it, then share to the community to prevent the same issues since even that Im quite experienced with OP devices but this is the 1st time I face this so it may be the new issue which comes with OOS13 or else.
Click to expand...
Click to collapse
Keep me posted if you are able to pin-point the exact issue.
-- We can always learn from each other with a helping hand.
rodken said:
Keep me posted if you are able to pin-point the exact issue.
-- We can always learn from each other with a helping hand.
Click to expand...
Click to collapse
Sure man, just like before, based on the information I have from our forum, I was successfully restore a dead OP 8T TMO with Testpoint trick after few months after it bricked. That thread, I believe still somewhere at 8T Forum
Daniha said:
You stil missed My POV. You need to visit service Center the only option left in this case. I can also fix but device need in hand.
Here everyone Provide you file but what if you're Not able to access 9008
Or another option is ufs dump
Click to expand...
Click to collapse
Pls kindly re-check my reply at #12
Anyone? Anyone have any information pls!!!
LinhBT said:
Anyone? Anyone have any information pls!!!
Click to expand...
Click to collapse
The device is most likely dead if it cannot enter EDL mode. There have been reports of issues entering EDL mode when using a USB 3 port, so trying a USB 2 port might be another option.
Xryphon said:
The device is most likely dead if it cannot enter EDL mode. There have been reports of issues entering EDL mode when using a USB 3 port, so trying a USB 2 port might be another option.
Click to expand...
Click to collapse
Tks mate, but I already aware of the USB 3.0 issue hence I always use USB 2.0 . And as I mentioned, I already accepted the fact that its dead ( more than dead )) ) Just I want to figure out what was really happened that make it dead so that we can warn the others since I guess that this comes from the smt inside the Ofiicial Oneplus OTA package.
LinhBT said:
Tks mate, but I already aware of the USB 3.0 issue hence I always use USB 2.0 . And as I mentioned, I already accepted the fact that its dead ( more than dead )) ) Just I want to figure out what was really happened that make it dead so that we can warn the others since I guess that this comes from the smt inside the Ofiicial Oneplus OTA package.
Click to expand...
Click to collapse
There is an interesting write-up regarding your issue.
Not to mention that there is the possibility of corrupting the Param Partition that will cause EDL to not function under the MSM Tool with the old param mismatch.
Hello everyone, I desperately need assistance because I think I may have soft bricked my work provided SM-A536B/DS.
What I tried to do initially is to install TWRP so I unlocked the bootloader successfully. Then, I saw different posts here on XDA where people have successfully installed cust ROMs so i tried to do that. This is when the problems started...
Right now my phone is bricked, I assume it is a soft brick because I can still get it to download mode. I did some research prior writing here, and everyone is mentioning to flash the stock ROM. That does not work.
Right now, the phone has bootloader unlocked: (Screen1)
It is asking me to lock it, so that means it's already unlocked.
Tried to access TWRP but I cannot since I get this screen when I do vol up + power: (Screen 2)
My phone was bought in Europe. I am not entirely sure whick ROM is the right one. Is there a way to check which is the right one to download? There are multiple ROMs I can download for Europe: (Screen3)
My country is not in the list so i downloaded the 2 generic for Europe. I put my phone in download mode: (Screen4)
However Odin fails everytime, no matter what files I add: (Screen5), (Screen6)
Since TWRP is not working, I locked the bootloader again to see if I could get Samsung bootloader to show up. I think i might have deleted it somehow, because I get the same thing as before when i do vol up + power. And as you can see, the bootloader is not locked: (Screen7)
I am now stuck and screwed, because this is my work phone. Any help is greatly appreciated.
psorincatalin87 said:
Hello everyone, I desperately need assistance because I think I may have soft bricked my work provided SM-A536B/DS.
What I tried to do initially is to install TWRP so I unlocked the bootloader successfully. Then, I saw different posts here on XDA where people have successfully installed cust ROMs so i tried to do that. This is when the problems started...
Right now my phone is bricked, I assume it is a soft brick because I can still get it to download mode. I did some research prior writing here, and everyone is mentioning to flash the stock ROM. That does not work.
Right now, the phone has bootloader unlocked: (Screen1)
It is asking me to lock it, so that means it's already unlocked.
Tried to access TWRP but I cannot since I get this screen when I do vol up + power: (Screen 2)
My phone was bought in Europe. I am not entirely sure whick ROM is the right one. Is there a way to check which is the right one to download? There are multiple ROMs I can download for Europe: (Screen3)
My country is not in the list so i downloaded the 2 generic for Europe. I put my phone in download mode: (Screen4)
However Odin fails everytime, no matter what files I add: (Screen5), (Screen6)
Since TWRP is not working, I locked the bootloader again to see if I could get Samsung bootloader to show up. I think i might have deleted it somehow, because I get the same thing as before when i do vol up + power. And as you can see, the bootloader is not locked: (Screen7)
I am now stuck and screwed, because this is my work phone. Any help is greatly appreciated.
Click to expand...
Click to collapse
This is why it's a bad idea to screw with work provided devices. You don't own the phone, and you will be held financially responsible for it if it's damaged or broken.
You're trying to flash the wrong firmware. You have G925F selected; your device is an A536B. The latest firmware for your device is A536BXXU4BVL2. Use Frija to download the latest firmware.
Since this is a work owned device, the only advice I will offer is this: Return the phone to stock with the correct software, re-lock the bootloader, and do not attempt to modify it as it is most likely in violation of your company's technology acceptable use policy.
V0latyle said:
This is why it's a bad idea to screw with work provided devices. You don't own the phone, and you will be held financially responsible for it if it's damaged or broken.
You're trying to flash the wrong firmware. You have G925F selected; your device is an A536B. The latest firmware for your device is A536BXXU4BVL2. Use Frija to download the latest firmware.
Since this is a work owned device, the only advice I will offer is this: Return the phone to stock with the correct software, re-lock the bootloader, and do not attempt to modify it as it is most likely in violation of your company's technology acceptable use policy.
Click to expand...
Click to collapse
Yes, this is what I am trying to do, to return to stock ROM. I downloaded A536BXXU4BVL2 for my phone, not G925F (this is what Odin uses as an example).
psorincatalin87 said:
Yes, this is what I am trying to do, to return to stock ROM. I downloaded A536BXXU4BVL2 for my phone, not G925F (this is what Odin uses as an example).
Click to expand...
Click to collapse
What version of Odin are you using?
Your bootloader is still unlocked, correct?
If you're unable to reflash the OEM firmware in Odin, I don't think there's anything else that can be done.
To be completely honest with you, I'm not sure trying to help you is worth the effort, because you did something you shouldn't be doing anyway, and any consequences you may face are entirely of your own doing.
V0latyle said:
What version of Odin are you using?
Your bootloader is still unlocked, correct?
If you're unable to reflash the OEM firmware in Odin, I don't think there's anything else that can be done.
To be completely honest with you, I'm not sure trying to help you is worth the effort, because you did something you shouldn't be doing anyway, and any consequences you may face are entirely of your own doing.
Click to expand...
Click to collapse
Yes, i know I did something bad and I learned my lesson.
I'm using Odin 3.14 and indeed, bootloader is still unlocked. I really appreciate the help!
psorincatalin87 said:
Yes, i know I did something bad and I learned my lesson.
I'm using Odin 3.14 and indeed, bootloader is still unlocked. I really appreciate the help!
Click to expand...
Click to collapse
I downloaded the firmware with Frija and I get the same issue with Odin.
psorincatalin87 said:
I downloaded the firmware with Frija and I get the same issue with Odin.
Click to expand...
Click to collapse
What options do you have checked in Odin?
V0latyle said:
What options do you have checked in Odin?
Click to expand...
Click to collapse
I haven't touched any of the options, everything is on default.
While reading this post something popped in my head.
I dont have this phone, but a Xiaomi Mi8.
When I want to adb push or sideload stuff into phone while it is in recovery or download mode, certain usb ports will work and others wont. And there is not a clear error when it's plugged to non-working usb port, just fails in the middle of a transfer with a generic error message.
Maybe totally irrelevant, just wanted to share.
nsfnd said:
While reading this post something popped in my head.
I dont have this phone, but a Xiaomi Mi8.
When I want to adb push or sideload stuff into phone while it is in recovery or download mode, certain usb ports will work and others wont. And there is not a clear error when it's plugged to non-working usb port, just fails in the middle of a transfer with a generic error message.
Maybe totally irrelevant, just wanted to share.
Click to expand...
Click to collapse
OH.MY.GOD! Thank you very much, man! I love you! I could kiss you right now, stranger!
Haha I'm glad it worked.
Hope you get better luck on your future rom adventures.
nsfnd said:
Haha I'm glad it worked.
Hope you get better luck on your future rom adventures.
Click to expand...
Click to collapse
Nah, this is my last one.
psorincatalin87 said:
Nah, this is my last one.
Click to expand...
Click to collapse
don't be that way lol, it's fun, just do it on hardware you own. get a cheap phone off ebay to play with
I am a very experienced ROM enthusiast and owned plenty of Xiaomi/Oneplus devices.. This is my first pixel device. I loved the phone, more than the other mentioned companies. My pixel 7 Pro was my prized possession.. I've came close a couple of times botching a ROM flash, even once with my p7p (installing evo with February firmware instead of Jan, phone would boot to bootloader for a total of 2 seconds before dying again, had to spam flash phone in pixel flasher app until it recognized and luckily it did) but this time, trying to go from latest feb build to jan before flashing evo, my ****ing cable did something in the middle of flashing the second partition (b partition) and was almost to system, the partition it flashes before booting.. it was flashing the product partition.. literally already flashed every other partition except partition and system on the b slot. A slot was fully flashed.. phone literally wont respond to plugging into computer, into charger, holding down every combination of buttons... doesn't matter. I'm stumped how flashing a factory rom could have gone this horribly.. especially so late into the flashing process..
Beware guys; Make sure the cable you're using to flash is stable!
attached in this post is the logs I have pulled from the pixel flasher app.. if someone could bounce some ideas off of me or somehow make this make sense to me, it would be gladly appreciated.
Holding down the down volume button when starting doesn't enter bootloader? If it does, use Google's online Android Flash tool to go back to stock.
Try a different cable.
Try a different USB port.
Try another computer as well.
If any of these prompt some response, I think there's hope. Also try booting into fastboot from bootloader as well as recovery.
Prob hard brick.
im wondering, since i am just flashing the feb factory image on my rooted pixel and read this thread here: if my laptop (from which i operate the flashing procedure) were to malfunction like it did last night (bsod) - would i hard brick my phone, too? isnt that, where the other slot comes into play?
does this mean, every time i flash, my pc/laptop should never run into any issues whilst flashing or otherwise my phone will be effed?
xflowy said:
im wondering, since i am just flashing the feb factory image on my rooted pixel and read this thread here: if my laptop (from which i operate the flashing procedure) were to malfunction like it did last night (bsod) - would i hard brick my phone, too? isnt that, where the other slot comes into play?
does this mean, every time i flash, my pc/laptop should never run into any issues whilst flashing or otherwise my phone will be effed?
Click to expand...
Click to collapse
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Arealhooman said:
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Click to expand...
Click to collapse
uff ok. is there any way to avoid this? i mean, even my desktop pc (which is stable) could suffer from a power shortage in the house for example.
xflowy said:
uff ok. is there any way to avoid this? i mean, even my desktop pc (which is stable) could suffer from a power shortage in the house for example.
Click to expand...
Click to collapse
Nope. Get a battery. If a flash fails, 75 percent chance ur ****ed (and yes, I am pulling these statistics out off my ass, but I doubt I’m too much off)
Arealhooman said:
Nope. Get a battery. If a flash fails, 75 percent chance ur ****ed (and yes, I am pulling these statistics out off my ass, but I doubt I’m too much off)
Click to expand...
Click to collapse
A battery for my desktop PC?
xflowy said:
A battery for my desktop PC?
Click to expand...
Click to collapse
Google for "uninterruptible power supply" ...
xflowy said:
A battery for my desktop PC?
Click to expand...
Click to collapse
Yeah, no idea.
Maybe I'm wrong, but although the whole flashing process can fail if communication with device breaks, it's hard to actually fail while flashing a partition? Because the system first pushes the whole file and only then does it begin actual flashing. So whatever partition you are pushing at any given moment, if it fails to push it in its entirety, then it won't flash it... Unless data is corrupted during transfer?
xflowy said:
im wondering, since i am just flashing the feb factory image on my rooted pixel and read this thread here: if my laptop (from which i operate the flashing procedure) were to malfunction like it did last night (bsod) - would i hard brick my phone, too? isnt that, where the other slot comes into play?
does this mean, every time i flash, my pc/laptop should never run into any issues whilst flashing or otherwise my phone will be effed?
Click to expand...
Click to collapse
Arealhooman said:
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Click to expand...
Click to collapse
The real answer to this is why google and the android community as a whole is pushing away from having a supporting third party recovery menu (implementing new partitions like init_boot and vendor_boot for recovery, also no working twrp). Why do you think Evolution ROM pushes so hard to be different and when flashing their newest build you do it not through the usual scary tedious bootloader way (THE SAME WAY WE ARE SUPPOSED TO FLASH OUR FACTORY ROMS) to making their own recovery, which obviously means only flashing one partition, and adb sideloading the rom. its like google wants you to break your phone and they are making it more convenient for third party roms to package theirs the same way. i should have never left evo.. haha.
Oh, and sorry for the late reply. I thought I would leave my phone alone for a little to see if it would help; I'm accident prone and lose things constantly, and what do ya know I just lost my phone that I can't even call to find lmao. Ill keep updated on everyones opinions on what i should try whenever i find it
krakout said:
Maybe I'm wrong, but although the whole flashing process can fail if communication with device breaks, it's hard to actually fail while flashing a partition? Because the system first pushes the whole file and only then does it begin actual flashing. So whatever partition you are pushing at any given moment, if it fails to push it in its entirety, then it won't flash it... Unless data is corrupted during transfer?
Click to expand...
Click to collapse
Google uses sparse images... I think they're maxed at like 262MB? So like you'll see the flashing process go Product 1, Product 2, etc... It flashes after the full sparse image is transferred but if you don't have the full image when something goes wrong, you can still brick.
EtherealRemnant said:
Google uses sparse images... I think they're maxed at like 262MB? So like you'll see the flashing process go Product 1, Product 2, etc... It flashes after the full sparse image is transferred but if you don't have the full image when something goes wrong, you can still brick.
Click to expand...
Click to collapse
Ah I see, makes sense.
xflowy said:
uff ok. is there any way to avoid this? i mean, even my desktop pc (which is stable) could suffer from a power shortage in the house for example.
Click to expand...
Click to collapse
Oh brother, how often does that actually even happen?
HipKat said:
Oh brother, how often does that actually even happen?
Click to expand...
Click to collapse
Sure, not really often. But when it does..
Arealhooman said:
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Click to expand...
Click to collapse
This is incorrect. The image is sent to the device memory (RAM) prior to actually being written. It won't write it to flash storage until AFTER the entire image is received.
zacattackkc said:
trying to go from latest feb build to jan before flashing....
Click to expand...
Click to collapse
It sounds like you may have tripped some anti-downgrade code.
EDIT: I can confirm that the bootloader version was changed in the FEB image as compared to the JAN image.
96carboard said:
This is incorrect. The image is sent to the device memory (RAM) prior to actually being written. It won't write it to flash storage until AFTER the entire image is received.
Click to expand...
Click to collapse
Well, I use Samsung, so I am assuming fastboot is similar…