Hi everyone,
After a crashed flash, my P1000 seems completely bricked.
I cannot access to download mode or recovery, I can't even turn it on.
I tried to let it charge during 4 hours : nothing...
I tried to let it connected in USB to see if Odin will finally retect it : nothing...
At the time, the only thing that makes me think it's not completely dead is that the screen turns on when it's charging : after a fex minutes charging, the screen shows this :
{
"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"
}
When it's like that, if I plug it in USB to my computer, I can hear it detect the device (usb connection) and I can even see 2 new volumes in the file explorer (I obviously can't access it).
I'm hesitating to try the unbreakable mod...
But if anyone have another idea...
Please help !
Thank you.
Same here, Odin failed towards the end for me. At least yours is still detected by the PC, mine is un detectable
Sent from my SGH-T999 using xda premium
Have you tried going into download mode when that charging screen shows up?
Also, can you describe the situation that led to the brick?
geno93n0 said:
Have you tried going into download mode when that charging screen shows up?
Also, can you describe the situation that led to the brick?
Click to expand...
Click to collapse
Hi, and thanks for helping !
So, to explain the situation :
Tha tablet was in this configuration :
Model gt-1000
micrologiciel 2.3.6
bande base p1000xxjpz
kernel 2.6.35.7 overcome-v4.0.0 #40
numero de version overcome 7 series v4.1.0
I tried to flash a CM10 Rom (this one : cm-10-20130428-NIGHTLY-p1) using CWM recovery : the flash succeed. But I had a lot of FC, Keyboard problems...So I reflash it again (full wipe), but the result was exactly the same. So I decided to go back to Overcome and I flashed using Overcome_7_series_v4.1.0_wipe.
During the flash, the tablet turned off...it was charging during all the process, so it was not a battery problem.
I turned it on and it booted directly into recovery. I tried to flash again with overcome, but I had a lot of errors...I restarted the recovery mode...and it never restarted again
Since this moment, I always have a complete black screen, except when charging as shown on the picture.
@geno93n0 : I tried to enter the download mode when the screen shows the battery, but it didn't worked. It just turned off the tablet.
As I've tried everything possible during 4 days, I decided to follow the unbrickable mod tutorial.
But now I'm stuck with a problem : I successfully removed the resistor, and hardware modification.
I ran the The Ultimate UnBrickable Resurrector and it seemed to succeed to turn on the device in download mode.
After that, I ran Heimdall One-Click : It found the device, and starts flashing...but it stops every times at 32% of Factory FS (Failed !) and I have no idea why...
Can someone helps ??
As long as you can get into Download Mode, something can still be done. If you already tried flashing GB-Stock-Safe from Overcome and failed, then maybe you should try your device's default stock ROM. The first priority is to see if you can get back to a working Android system, so trying to restock would be the best starting point. If you run into Checksum Errors when restocking, flash dbdata.tar as PDA.
Also, have you tried waiting a little bit longer when OneClickUnbrick stops? I seem to remember that happening to me as well, though I only had to wait it out. Also, OneClickUnbrick should generally only be used if you get the phone-!-computer screen.
Lastly, I also had problems flashing that CM10 nightly, but that was actually because I put the zip in the external SD, and not the internal one. So once you get back into a working system, double-check the locations of everything.
Thank you very much for trying helping me.
But as I said, I can't access to any mode with the tablet : nor download or recovery mods.
I made the hardware modification, but I'm not even sure my welding is good...
So the only way to access download mod for me is to follow the steps in this thread : http://forum.xda-developers.com/showthread.php?t=1312391
I followed every steps.
Here is the log of Ultimate UnBrickable Resurrector :
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Apply UnBrickable Mod
2. Remove then insert Device battery
3. Connect to computer via USB.
4. Click the Download Mode button
5. Download new software with Heimdall.
Credits:
AdamOutler- Hardware Analisys/Modification/high level software development
Rebellos- Firmware development
Midas5, mijoma, TheBeano- UART Output Debugging/Firmware Support
Building command list
--S5PC110 (Galaxy S) selected, Resurrector HIBL.bin to 0xD0020000
Secondary Bootloader Sbl.bin to 0x40244000 through SMDK
Begin Resurrection Sequence
Requesting Permission to access device
Please wait.... Uploading..
-------------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v2.1
Copyright (C) Rebellos 2011
-------------------------------------------------------------
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
S3C64XX Detected!
=> found device: bus 001, dev 110
=> loaded 24576 bytes from /tmp/alexandreHeimdallOneClickDC57D886/UnBrickPack/HIBL.bin
=> Downloading 24586 bytes to 0xd0020000
=> Data checksum d8dc
=> usb_bulk_write() returned 24586
Interceptor Injection Complete. Injecting modified SBL
SMDK42XX,S3C64XX USB Download Tool
Version 0.20 (c) 2004,2005,2006 Ben Dooks <[email protected]>
S3C64XX Detected!
=> found device: bus 001, dev 111
=> loaded 1310720 bytes from /tmp/alexandreHeimdallOneClickDC57D886/UnBrickPack/Sbl.bin
=> Downloading 1310730 bytes to 0x40244000
=> Data checksum f37e
=> usb_bulk_write() returned 1310730
Modified SBL Injection Completed Download Mode Activated
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
So, the device turns on, the flash light turns on too, and as the log shows, it seems to be in download mode.
Next to that, I ran the Heimdall One-Click to flash firmware and here is the log :
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Operating System: Debian Based x86_64
Found Heimdall Version: v1.3.1
Device not connected.
Total PITEntry Count: 15
Pit Complete.
Partition Targeted:0-IBL+PBL
Partition Targeted:3-SBL
Partition Targeted:4-SBL2
Partition Targeted:21-PARAM
Partition Targeted:6-KERNEL
Partition Targeted:7-RECOVERY
Partition Targeted:22-FACTORYFS
Partition Targeted:24-CACHE
Partition Targeted:3-SBL
Partition Targeted:0-IBL+PBL
GalaxyTab Stock P1000 XXJQ1 XXJPZ is ready for your device.
Ready for flash.
Total PITEntry Count: 15
Pit Complete.
Partition Targeted:0-IBL+PBL
Partition Targeted:3-SBL
Partition Targeted:4-SBL2
Partition Targeted:21-PARAM
Partition Targeted:6-KERNEL
Partition Targeted:7-RECOVERY
Partition Targeted:22-FACTORYFS
Partition Targeted:24-CACHE
Partition Targeted:3-SBL
Partition Targeted:0-IBL+PBL
[heimdall, flash, --pit, /tmp/rootHeimdallOneClick33D6EFDC/gt-p1000_mr.pit, --6, /tmp/rootHeimdallOneClick33D6EFDC/zImage, --7, /tmp/rootHeimdallOneClick33D6EFDC/zImage, --22, /tmp/rootHeimdallOneClick33D6EFDC/factoryfs.rfs, --24, /tmp/rootHeimdallOneClick33D6EFDC/cache.rfs]
Device not connected.
Ready for flash.
Total PITEntry Count: 15
Pit Complete.
Partition Targeted:0-IBL+PBL
Partition Targeted:3-SBL
Partition Targeted:4-SBL2
Partition Targeted:21-PARAM
Partition Targeted:6-KERNEL
Partition Targeted:7-RECOVERY
Partition Targeted:22-FACTORYFS
Partition Targeted:24-CACHE
Partition Targeted:3-SBL
Partition Targeted:0-IBL+PBL
[heimdall, flash, --repartition, --pit, /tmp/rootHeimdallOneClick33D6EFDC/gt-p1000_mr.pit, --0, /tmp/rootHeimdallOneClick33D6EFDC/boot.bin, --3, /tmp/rootHeimdallOneClick33D6EFDC/Sbl.bin, --4, /tmp/rootHeimdallOneClick33D6EFDC/Sbl.bin, --21, /tmp/rootHeimdallOneClick33D6EFDC/param.lfs, --6, /tmp/rootHeimdallOneClick33D6EFDC/zImage, --7, /tmp/rootHeimdallOneClick33D6EFDC/zImage, --22, /tmp/rootHeimdallOneClick33D6EFDC/factoryfs.rfs, --24, /tmp/rootHeimdallOneClick33D6EFDC/cache.rfs]
Device not connected.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
As you can see, the P1000 is detected as a S5PC110 (Galaxy S)
But as said in this post : http://forum.xda-developers.com/showpost.php?p=24341888&postcount=95
I think it should be detected as S5PC111 and it's not my case...
The Heimdall One-Click uploads some things to my device, and when coming to FACTORY FS, it justs stops at 32%.
As it's said in the related post, I made it a second time checking the Flash Bootloader.
It starts to upload PIT and stop immediately.
So...I really don't know what to do next
I'll paste the same post on the other thread, just in case...
That's a bit weird. From the very beginning it says Device not connected. But based on first-hand experience I've found that you can't use Odin and Heimdall simultaneously without first uninstalling the drivers they install.
Try running the zadig.exe that comes with Heimdall to install the driver (device must plugged in and in download mode). Click Options -> List all devices and install the Samsung USB composite device.
Failing that, go to your system tray, right-click Safely remove hardware, open Devices and look for Samsung USB Composite Device, then right click and remove it. The above case is if Odin won't detect your device.
Sent from my GT-P1000 using xda app-developers app
Related
Hi all,
My i9000 cannot boot successfully, it repeats the samasung logo again and again.
And when I try to re-flash the stock rom - 20110531_ZSJV5_2.3.3_ROOT_STOCK by ODIN
After reboot, it shows following Error:
E:failed to mount /data (File exists)
E:delete_data_files:Can't mount /data
your storage not prepared yet. please use UI menu for format and reboot action.
Media files copy failed
Click to expand...
Click to collapse
Then it keeps repeating the samasung logo again and again.
Please help!!!!
Can you access the download screen (volume down + home + start) or CWM screen (volume up + home + start)?
If you can access the download screen, use Odin and download the stock Gingerbread from online (do google search), make sure you also have a PIT file like PIT 512 or something, and have the re-partition ticked, try that and see if it fixes the problem.
If you access CWM, maybe voodoo lag fix is on and didn't properly format the partitions.
Thanks
I have tried using ODIN 1.8 and I9000ZSJV6
But the problem still retain
The screen shoot :
{
"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"
}
You need to get a .pit file (512) and use repartition in Odin when you are flashing the original rom.
Yeah~I have used PIT512 and selected Re-partition, but problem still remain........
Damn ... it looks bad.
I have a suggestion.
Push a speedmod kernel with odin.
Enter recovery mode.
Convert the partitions to RFS (even if they are reported as such).
Redo the flashing of the original rom.
O...situation goes really bad
After I have flashed SPEEDMOD, I enter CWM
and try to convert to RFS, it said:
Can't mount /mnt/sdcard
Backup failed!
Then quit.
And I try to mount internal SD,
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblo0)
(No such file or directory)
Error mounting SDCARD:!
It looks like you have issues with the nand memory. I'm not sure 100% about it but it sounds like this.
In case your nand flash is dead, I really don't know what can you do ... there are few topics related to this issue. Check them out and see maybe is a solution somewhere.
don't use JV6, try flashing using JVQ, and don't use rooted versions, use a pure stock, try using Odin 1.7. It if can't mount, maybe there's a corrupt internal SD.
You may want to look at the stock rom vs an odin custom rom (like darkys resurection edition) and see if everything that that the custom has (minus the mods) is in there. I would get a mounting error for db_data from my stock rom (drove me nuts) because the stock roms did not update that and there for with a re partition it was missing.
I finally found another post on the CM7 forums that mentioned it so it could be an issue for your rom too?
If you determine which file it might be you can pull it from an earlier stock rom (one of them should have it).
You might even try flashing darky's. if it works then you know its a file issue and the phone is likely fine.
G
I flashed over 10 different roms with re-partition but nothing change...........
but luckily warranty should still cover, it is now in factory.....
Thanks All~
Similar problem: Phone stuck in boot up loop
Okay so about 2 months ago rooted and put a new rom on my vibrant. Last night I decided I wanted to go back to the original stock rom by restore my phone back to its original factory settings (at the time it made sense to me). I did this by turning the phone off, holding the volume buttons and power button until a menu came up where I selected wipe to factory setting. In doing this I cleared the rom I had on my phone and am now stuck in a loop where my phone keeps trying to turn itself on but has nothing to boot up. I am able to get to the menu that enables me to wipe my phone to factory setting etc but that hasnt helped all too much. I'm unable to mount my phone now on my mac in order to put a new rom on the sd and Oden does not seem to work for macs and I do not want to put a virtual machine on my computer but will if thats the only solution. PLEASE PLEASE PLEASE HELP!
That doesn't wipe to factory settings if you had a custom rom. It just wipes the user areas so IF you had a stock rom it would be back like day 1 but with a custom rom its like day 1 of the custom rom.
Though something else happened here too.
G
Sent from my GT-I9000M using XDA Premium App
Don't use a mac use Odin and do it on windows, download the stock jvq rom again except in windows and use the 512 pit file aswell. See if that works.
Sent from my GT-I9000 using XDA App
Also forgot to mention when using Odin in windows make sure you have the windows drivers by downloading Samsung kies. From the Samsung website.
Sent from my GT-I9000 using XDA App
Hello, I have a little problem after installing clockworkmod with tutorial inside this page http://forum.xda-developers.com/showthread.php?t=1774560 (can't post outside link)
Instructions:
First time flashing CyanogenMod 10 your device, or coming from another ROM?
1. Root the device and install ClockworkMod Recovery. Instructions are available here.
Code:
Installing the ClockworkMod Recovery
This guide applies to a Samsung Galaxy Tab (GSM) on the stock 2.3 release. If the Samsung Galaxy Tab (GSM) already has the ClockworkMod Recovery installed, skip this section.
Warning: Installing a custom recovery image on the Samsung Galaxy Tab (GSM) will void the warranty.
Download Technomancer's kernel with the ClockworkMod Recovery and the Heimdall Suite:
Technomancer's Kernel with the ClockworkMod Recovery 5: Download
md5: e67e61a27741069e43bf9f790bf35b10
Windows:
Heimdall Suite 1.3.2: Download
NOTE: The Heimdall Suite requires the Microsoft Visual C++ 2010 Redistributable Package installed on the computer, which can be downloaded here.
Ubuntu 32bit:
Heimdall Suite 1.3.2 Command-line Binary: Download
Ubuntu 64bit:
Heimdall Suite 1.3.1 Command-line Binary: Download
Mac OS X:
Heimdall Suite 1.3.2: Download
NOTE: The source code for the Heimdall Suite is available on Github.
Windows ONLY:
Power off the Samsung Galaxy Tab and connect the USB connector to the computer but not the Samsung Galaxy Tab.
Boot the Samsung Galaxy Tab into download mode by holding down Power and Volume Down while connecting the USB connector to it.
Run the included zadig.exe in the drivers folder of the Heimdall Suite.
From the menu, choose Options » List All Devices.
From the drop down, select Samsung USB Composite Device or Gadget Serial.
Click Install Driver.
NOTE: A prompt may appear warning that the installer is unable to verify the publisher of the driver. Ignore it and select "Install this driver anyway."
Heimdall can now be used safely on the Windows computer.
NOTE: For more information about the Heimdall Suite, please read the included README.txt.
Power off the Samsung Galaxy Tab and connect the USB connector to the computer but not the Samsung Galaxy Tab.
Boot the Samsung Galaxy Tab into download mode by holding down Power and Volume Down while connecting the USB connector to it.
Untar Technomancer's kernel into the Heimdall directory.
On the computer, open terminal and run the following command from the Heimdall directory:
heimdall flash --kernel zImage
A blue transfer bar will appear on the device showing the kernel being transferred. The device will reboot automatically.
The Samsung Galaxy Tab now has the ClockworkMod Recovery installed. Continue to the next section.
After reboot I'm stuck on Galaxy Tab Samsung screen. I can reach clockworkmod and download mode. Is there something to worry about or I can just continue installing cm10?(when i launch clockworkmod it displays a few comunicates
E:can't mount /cache/recovery/command
E:can't mount /cache/recovery/log
E:can't open/cache/recovery/log
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
cmd log:
Microsoft Windows [Wersja 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. Wszelkie prawa zastrzeżone.
C:\Users\Bardys>cd c:\Users\Bardys\Desktop\Galaxy Tab\heimdall-suite-1.3.2-win32
\Heimdall Suite
c:\Users\Bardys\Desktop\Galaxy Tab\heimdall-suite-1.3.2-win32\Heimdall Suite>hei
mdall flash --kernel zImage
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
100%
KERNEL upload successful
Ending session...
Rebooting device...
c:\Users\Bardys\Desktop\Galaxy Tab\heimdall-suite-1.3.2-win32\Heimdall Suite>
edit:1
Flashed clockworkmod on gingerbread previously updated via kies from froyo
Version of clockworkmod: 5.0.2.8
Any help much appreciated
For those come from non ICS MTD rom, such as yourself from froyo,
You need to flash cm10 twice.
First round installs new cwm and converts to mtd.
Second round the rom itself.
So, just boot to cwm again, and flash cm10 again.
Sent from my GT-P1000 using xda app-developers app
By flashed i mean i have flashed only recovery yet.
Oops. Yes, then you should flash.
Weird you can't go download mode.
Sent from my GT-P1000 using xda app-developers app
I can, i created this thread because my stock rom isn't working after install of recovery and im curious why and to know if im safe to begin install of cm10
edit1: I found something, that can be related http://forum.xda-developers.com/showthread.php?t=1841748
gogol1996:Well, the problem is that the bootloop occurs if the cwm i mentioned is flashed in the firmware of gb stock safe package. so i recommend against it
Maybe that is the case but what can I do now?
Well you saw my post there too.
I can't say enough.
Overcome method works 100% where cf root fails sometimes.
When you said you can't go to download mode, what actually showing.
Sent from my GT-P1000 using xda app-developers app
I can access download mode, I just can't boot stock rom
Bardys said:
I can access download mode, I just can't boot stock rom
Click to expand...
Click to collapse
then you must continue the installation
There is something else about I forgot, because I installed recovery when the battery was about 40%i didn't have to worry about this, but now because I was checking recovery and download mode it's about 20% I think. When I plug the charger it displays battery whith circle but its not showing the state of battery, is it charging or not and if not will it charge in download mode/recovery?. And because I can't boot stock rom I can't access internal sd, can I use external from my wildfire S to place cm10 rom file and install via recovery?
{
"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"
}
not sure about the charging from recovery/download.
But you can always powered it all down and charge.
yes you can download using your other phone.
but make sure it is not corrupted (I prefer to download using PC if possible)
I want to download using PC and transfer it to wildfire s sd card. You mean I have to deplete the battery completely? It's little risky, because if I then wont be able to charge it it's over. The tab is off when i plug the charger.
not sure about that part. Probably just battery charging animation. Just leave it charging for a few hours then do your flashing.
You are not flashing the bootload (since you are not using Odin), so it is unlikely you can screw up the bootloader. So it should be always possible to revive should anything go wrong. Unless there is hardware issue to start with.
Ok, I'll do as you say (for charging battery is responsible bootloader or Rom?)
I am not a dev. But I remember that certain battery charging animation pictures are in kernel. One of the cm9 humberos kernel has broken battery picture briefly when plugged in.
Sent from my GT-I9300 using xda app-developers app
Ok, I want just to make sure, that the charging script isn't damaged because if yes, the tab is just depleting(screen doesn't go off while charging)
edit1: That what I get in recovery:
I tried also HumberOS http://www.humberos.com.br/2012/08/cm10-20120823.html ,the same result.
What was your tab running before this? What model is it. What does it say at the back. The assert function says you are not P1000.
Did you do the whole GB stock safe v5 + overcome kernel.
If not, you should. That should correct the detection.
The alternative is to unpack the rom and find the updater script deep in META-INF folder and remove the assert lines....
Sent from my GT-P1000 using xda app-developers app
Model: GT-P1000
I said I was on stock GB, I will try restocking.
Not any restocking.
You want overcome method.
Sent from my GT-P1000 using xda app-developers app
You mean, that I should do from Overcome site http://www.teamovercome.net/p1000/?page_id=17 point "Re-“Stocking” Yer System…" or "Installin’ The Overcome ROM…" ?(just want to make sure) and have I to have Kies installed before using Odin?
root created by phifc, original ezSBF by 1kds, and modified by bhigham
ezSBF and root cd
Droid_X_621-ezSBF-and-RootCD.iso (225MB) MD5: c4961b5b93aa1b2881023d3f3e3f4ea4
Dev-Host - Droid_X_621-SBF-and-RootCD.iso - The Ultimate Free File Hosting / File Sharing Service
Download Droid_X_621-SBF-and-RootCD.iso from Sendspace.com - send big files the easy way
https://docs.google.com/file/d/0B1hcBgk_03_aS0hldl94Zzd3WjQ/edit?usp=sharing
How to verify the file was downloaded correct with
MD5/SHA-1 Hash Checksums
Root Only option
Droid2_D2G_DX_DX2-RootCD-2012.iso(54mb)md5 Hash:7BAEE9C34F6EF7AD0B4FA219AE387C68
Droid2_D2G_DX_DX2-RootCD-2012.iso
https://rapidshare.com/files/1493446314/Droid2_D2G_DX_DX2-RootCD-2012.iso
https://docs.google.com/file/d/0B1hcBgk_03_aU1Bpc0VuQUJfQnc/edit
what is ezSBF?
original [TOOL] ezSBF (not for 2.3.4)
1KDS said:
Don't let the word Linux scare you, this is just a cd you burn, nothing installs to your pc. Once you burn this CD you are ready to SBF flash anywhere you have a computer, no net connection needed to download any files.
This is an .iso file. It is a complete Linux operating system that you will download, burn to CD (or USB) then boot your pc from CD or USB, this allows your pc to reboot into a different operating system.
Click to expand...
Click to collapse
1KDS said:
Instructions (Mac):
Download .iso
Use Disk Utility (built in) to burn iso file to a CD (instructions)
Shut computer down
Hold c key, push power and hold c until you see the Linux OS start
Hit enter at the yellow "boot baby... boot" screen
You will see yellow dots for 3-5 minutes then the script will start
Instructions (Windows):
Download .iso
Burn iso image to a disk (Instructions, Windows 7 - Vista and XP)
Reboot PC
Hit F12 (sometimes F8 or esc) during boot to go to boot menu (possibly google search how to boot your specific pc from CDROM)
Select boot from CDROM (or USB if you used a flash drive)
Hit enter at the yellow "boot baby... boot" screen
You will see yellow dots for 3-5 minutes then the script will start
Live USB Instructions (Windows):
(Instructions from pendrivelinux.com)(thanks)
Download UNetBootin for Windows
Download your favorite Linux ISO
Double click the Unetbootin Executable to start the program
(1) Click the Diskimage radio box
(2) browse to select your ISO
(3) Set your target USB drive
(4) click OK to start the creation
{
"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"
}
(5) After the USB drive is done select reboot.
(6) During boot enter the boot menu and change USB to boot first, save and reboot.
(7) When booting from UNetbootin select SliTaz
Click to expand...
Click to collapse
if cd/usb flash drive is made correctly you will not have Droid_X_621-ezSBF-and-RootCD.iso or Droid2_D2G_DX_DX2-RootCD-2012.iso on cd
you will have a folder named 'Boot'
with two files and a folder in the boot folder
usb flash drive may have a few more files
Hit enter at the yellow "boot baby... boot" screen
You will see yellow dots for 1-3 minutes then the script will start
root only
ezSBF and root
basically read onscreen directions
don't use numbers on right side of your keyboard, just use the ones above qwerty
select flash sbf only if phone is not working correct or you do not have 621 on phone yet
follow onscreen directions
root
select root DX
follow onscreen directions
turn phone on, connect to pc with usb cable
check usb debugging (settings/apps/development)
select charge only usb mode in top status bar
press continue
adb will push
Code:
data/local.prop /data/preinstall_md5/magic.md5
program will prompt you to
manually reboot phone to bootloader (Hold volume up+down buttons and power button, or hold Vol.Down and Camera and wait for the screen to flash)
program will will be flash repacked sbf (less than 50mb)
Program will reboot phone twice, very important (reboot just replaces the local.prop, but the old local.prop is still in memory, till second reboot)
adb pushes su,superuser, and busybox
program will reboot to recovery,
manually wipe cache (should auto reboot to recovery, at android andy press both volume buttons, if it doesn't press home button and hold it in then press your power button, hold it in also till you see a triangle on the screen w/ android andy then press both volume buttons)
then select reboot
rooted
error info
when running the program you may see these errors
rm failed for /data/preinstall_md5/magic.md5 no such file or directory
no root.img.gz no such file or directory
rm failed for /data/preinstall_md5/magic.md5 read only file system
that is fine, it will still work
after flashing files in bootloader, phone reboots to bootloader, instead of normal android operating system..... now what?try disconnecting usb, pull battery,wait a few secs, replace battery, reboot, wait for reboot to complete, reconnect usb
don't want to reboot pc try
Using Oracle VM VirtualBox, and Magic MD5 root iso
If you planning on making nandroid backups or flashing roms
read [HOW TO] Install/Use Droid 2 Bootstrap
bhigham/beh modified the root method
based on New D2 root method for stock 2.3.4 (621/622) found (Droid2, R2D2)
How this works
Originally Posted by phifc
There's an exploit in loadpreinstall.sh. It compares md5 sum files of preinstalled apps and if they're different, copies the md5 to the local cache. The preinstall just has an empty file in app/ so it will parse the md5 for it. Instead of an md5 sum, it contains a local.prop that allows adb root shell. So the system thinks it's copying the md5sum to the cache when it bounces off the symlink and overwrites the /data/local.prop, giving adb root on next reboot
Click to expand...
Click to collapse
originally posted by bhigham/beh
Since all these devices (Droid 2/R2D2/D2G/DX2 and DX seem to be vulnerable to the same exploit found by phifc at
http://rootzwiki.com...nd-droid2-r2d2/
I have assembled rooting methods for all of them in EzSbf style CD. I have tested it on my D2G, and the same method has been tested by multiple users on the D2/R2D2, and has worked fine.
Credit for this method go to phifc, djrbliss, and the others who developed the method.
I have simply taken the method, and assembled the tools.
Credit for the idea behind the CD method should go to 1KDS, as I have mostly patterned this CD after his method.
Credit should also go to Skrilax_CZ, as without his Motorola Android Firmware (De)packer, we wouldn't be able to have a 55 meg CD that covers multiple devices.
Special thanks also to themib for testing and troubleshooting on the DroidX2. In fact, since I don't have a DX2, he actually did a majority of the work in finding a method that would work (the method for the D2 and D2G doesn't quite work), and then we worked together to get it assembled and working.
This CD is for the D2,R2D2, D2G, and DX on Android version 2.3.4, and the DX2 on 2.3.5.
One note if you have troubles with it not working. It might be necessary to disconnect the phone after it flashes the preinstall and reboots. It seems that some phones may not complete the reboot process before being rebooted by ADB, so you may need to disconnect the phone when it starts booting, and let it boot fully before hooking it back up. when hooked back up, it will be rebooted, and should go on with the process like normal.
Of course, like all other things here, I have done my best on this, but there are no guarantees, and anything you do on your phone is at your own risk.
Click to expand...
Click to collapse
My Lists
Magic MD5 Root 2.3.4 for D2, R2D2, D2G, DX and 2.3.5 for DX2 - Google Docs
sd_shadow's [Collection] of Links: FAQs, Guides, Rooting, SBFs, ROMs... - Google Docs
[Video] How to Root Droid X on Android V2.3.4-Tomsgt123
Droid_X_621-SBF-and-RootCD-2nd_edition.iso 225.00 MB
other version had incorrect instructions, for boot to recovery, after flashing sbf
[ROOT] Framaroot, a one-click application to root
I have verified it works with these Motorola devices running android 2.3.4
Droid 2 (a955), Droid 2 Global (a956), R2D2 (a957), & Droid X (MB810)
Just download, allow unknown sources, install, open, select top root method (Gimli), reboot phone, done
no pc needed
I can also confirm, Framaroot works with with essentially one touch, at least for .621.
Sent from my Inspire 4G w/CM10.1
Bump
Sent from my Amazon Kindle Fire using Tapatalk
sd_shadow said:
Bump
Sent from my Amazon Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Thank you for this by the way. I pulled my DX out of retirement to try CM11 and not everything went as planned. I remembered I had an old sbf disk tried that it turned out to be 605 which of course resulted in a bootlader error. I was able to use 621 restore and root to recover from disaster. :highfive:
[Resource/DevTools] TheCollectiveHelpPackageSCH-i800[everything you need & some]72813
{
"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"
}
TheCollective SCH-i800 Help package
http://wiki.cyanogenmod.org/w/P1c_Info
---------------------------------------------------------------------------------------------------------------------------------------------
TheCollective is Proud to present to you StockRooted-sch-i800 Verzion Galaxy Tab
For what ever reason we all need to get back to the default factory state.
soft brick
resale
loss of stablity
to name a few.
Here are the steps you will need to take.
First let's point out that this package contains EVERYTHING YOU NEED for this Except the windows PC to which it will be used on.
Before we begin Install Samsung usb device drivers located in the package.
**\tools-resources\drivers
Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0
next is unpacking Hemdall 1.3.2 (The only one that worked for me on my SCH-i800)
**\tools-resources\Heimdall\
heimdall-suite-1.3.2-win32.zip
But here is a link to the developers page so you can download the original/newer if you want.
http://www.glassechidna.com.au/products/heimdall/
You will also need *Microsoft C++ 2012 32bit [if 2013 32/64bit has already been installed you will need to remove it first to install 2012]
This needs installed on your machine because it has .dll files Heimdall uses.
**\tools-resources\MicrosoftC++12\
vcredist_x86.exe
Now you will need to install the drivers this is also needed for Heimdall.
unzip heimdall and go into the drivers folder where you will see /zadig.exe. Run this.
At the top you see options. Click "list all devices"
Then in the dropdown select Android USB composite device (or whatever it says, eg genirc serial device) (tho NOT massStorageDevice)
[good idea to remove any other usb devices as they can and sometimse do interfere with the packet data sending/receiving]
Click the button "replace driver" and let heimdall download/install the drivers. {libusb0 is the one that worked for me, but try another if it dont for you, there are three}
Run Heimdall-Frontend.exe as admin
Files provided To Flash Your Tab with
**\TheCollective-StockRooted-sch-i800.tar.gz >--TheStockRooted 2.3.5 that came on your tab.
**\tools-resources\HumberOS\heimdall-uses
boot.img >-- a CM10.1 kernel with TWRP for sch-i800
recovery.bin >-- CM10.1 twrp for sch-i800
if you need the pit file --> my-sch-i800.pit [extract it from the stock tar gz]
Ok, Let's get to flashing over the files and getting your tab back to normal.
1: Connect your tab to your PC
2: Launch your tab into download as it is already connected to your PC.*(Do this by holding the volume down and pushing the power button)
3: Go in to the folder "Heimdall" and start " heimdall-frontend.exe" as ADMIN
4: Set up the file you are about to LoadPackage tab. [It should look something like image.]
5: After you have the file in place click load, it will change tab to flash with files listed, simply click start to flash.
ALWAYS make sure your battery is sufficiently charged or you will have MAJOR problems.
Tab should boot. [if not factory data reset in recovery e3 and reboot]
Click to expand...
Click to collapse
After this is should be just like you took it out of the box, and already rooted.
Hope this helps!
---------------------------------------------------------------------------------------------------------------------------------------
If you wish to unroot I've included SuperOneClick shortfuse.
just hit unroot
If you wish to install CM or other AOSP rom here is some helpfull info.
Heimdall command line
Flash boot.img with heimdall command line like this:
Press Power + VolDown untill you get the Download screen or PC <–> Tab screen.
on PC open CMD prompt in the folder of Heimdall and place boot image in same folder
type this command string:
Code:
heimdall flash --kernel boot.img --recovery boot.img
Or just replace boot.img inside the ROM ZIP with your desired kernel.
*TIPS
In case you get any strange symptoms.
Flash full TheCollective-StockRooted-sch-i800.tar.gz (with repartition) via Heimdall.
Flash the Kernel included in the package using the heimdall command above.
Boot directly into CwM Recovery, holding Power + VolUp.
Flash CM10.1 ROM, if it reboots by itself repeat the step above.
If you want Google’s stuff, flash latest GApps for Android 4.2.2.
Only Reboot after everything.
Wrong MAC? Wrong IMEI? Try restoring files from /sdcard/backup/efs*/* to /efs/. If you don’t have a backup, then start over with FULL Restock, and next time save your backup/efs folders, which are created everytime you install CM10.1.
Market problems? Clear Google Services Framework data and reboot.
No touch? That means you got the wrong kernel installed. A couple of builds had problems identifying the exact model. Just flash your kernel through recovery or heimdall / odin.
No boot? Stuck at the SAMSUNG logo? Flash the correct kernel using Download Mode using heimdall!
Deep Sleep not kicking in? Try wiping cLock’s data or freezing / removing it (com.cyanogenmod.lockclock).
--------------------------------------Highlights of What you get inside---------------------------------------------------------------
**\TheCollective-StockRooted-sch-i800.tar.gz
The Heimdall package
**\tools-resources\drivers\Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
Samsung Mobile Drivers for usb
**\tools-resources\Heimdall\heimdall-suite-1.3.2-win32.zip
Heimdall
**\tools-resources\HumberOS\heimdall-uses\boot.img
CM10.1 humberOS Kernel P1c
**\tools-resources\HumberOS\heimdall-uses\recovery.bin
TWRP Touch Recovery 2.5.0.0
**\tools-resources\HumberOS\CwM_CM10.1-humberos_kernel_p1c-20130715.zip
CM10.1 humberOS Kernel P1c
**\tools-resources\MicrosoftC++12\vcredist_x86.exe
Microsoft C++ redisturbutial
**\tools-resources\ODIN-1.7\
Odin3 v1.7.exe
If you need it for modems or kernels
**\tools-resources\PartitionTool4microSD\pwhe8.exe
if you get encryption failed, you might find this usefull to partition your external sdcard [deeper instruction online at rootzwiki]
**\tools-resources\SuperOneClick\SuperOneClickv2.3.3-ShortFuse.zip
unroot/root what ever just good to have hard to find
DOWNLOAD
MD5 Sum: F0F9C9FA54219EDFA50E85163D9A7C54
Excellent job of documentation! Thanks for all the hard work.
I come up with an MD5 of f0f9c9fa54219edfa50e85163d9a7c54 Anyone want to confirm?
robjective said:
Excellent job of documentation! Thanks for all the hard work.
I come up with an MD5 of f0f9c9fa54219edfa50e85163d9a7c54 Anyone want to confirm?
Click to expand...
Click to collapse
F0F9C9FA54219EDFA50E85163D9A7C54
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4 Beta
Appreciate the thread! Is it possible to get a mirror though? The current host keeps cutting me off whenever I try to download the file... Can't make it past 200MB no matter what I try; other files download fine.
Going through the whole process but "Heimdall.exe" stopped working EVERY time I press start. Any ideas?
Cellulah said:
Appreciate the thread! Is it possible to get a mirror though? The current host keeps cutting me off whenever I try to download the file... Can't make it past 200MB no matter what I try; other files download fine.
Click to expand...
Click to collapse
I had the some problem. Tried it at work with FF, Chrome, and Free Download Manager and all would fail at some point after about 2/3 done.
Came home and tried and got it first try.
tinpanalley said:
Going through the whole process but "Heimdall.exe" stopped working EVERY time I press start. Any ideas?
Click to expand...
Click to collapse
Perhaps bad DL.
Make sure you follow all instruction.
Don't skip any steps.
Don't forget to have the correct ms c++ redist istalled.
Sent from my GT-P5110 using Tapatalk 4
Johnsondr80 said:
Perhaps bad DL.
Make sure you follow all instruction.
Don't skip any steps.
Don't forget to have the correct ms c++ redist istalled.
Sent from my GT-P5110 using Tapatalk 4
Click to expand...
Click to collapse
I'll try again. The download was fine but I suppose I could try again.
No use.. same error every time . Tried with each driver as well. All I get is this:
tinpanalley said:
No use.. same error every time . Tried with each driver as well. All I get is this:
Click to expand...
Click to collapse
Tell me more about your operating system that your using.
Sent from my GT-P5110 using Tapatalk 4
Johnsondr80 said:
Tell me more about your operating system that your using.
Sent from my GT-P5110 using Tapatalk 4
Click to expand...
Click to collapse
Windows 7, 64-bit
Intel i5-2400 3.10 GHz
Just a question. Every time I boot to recovery <3e>, and try to wipe data, I get the following:
E:failed to mount /data (Invalid argument)
E:install_application_for_customer: Can't mount /data
your storage not prepared yet, please use UI menu for format and reboot actions
Could this have anything to do with why I'm not able to get out of my bootloop?
tinpanalley said:
Just a question. Every time I boot to recovery <3e>, and try to wipe data, I get the following:
E:failed to mount /data (Invalid argument)
E:install_application_for_customer: Can't mount /data
your storage not prepared yet, please use UI menu for format and reboot actions
Could this have anything to do with why I'm not able to get out of my bootloop?
Click to expand...
Click to collapse
Yes. I had same issue on my captivate trying to restore stock from a cm7
To fix I had to flash in the kernel and recovery from cm and in cwm under advance mounts format data. Back then on that device speedmod kernel allowed users to select format method (fat32/ext4/etc)
But also hemidall should format with the repartition. But that is assuming it can read and mount the partition.
You can use this package but instead of flashing the ROM package,
Load the pit and load only the kernel and recovery
Then boot into cwm and mount and format data (might as well while your at it mount and format system, and cache)
Sent from my GT-P5110 using Tapatalk 4
Johnsondr80 said:
You can use this package but instead of flashing the ROM package,
Load the pit and load only the kernel and recovery
Then boot into cwm and mount and format data (might as well while your at it mount and format system, and cache)
Click to expand...
Click to collapse
I did try this but I still get the crash of heimdall.
Also what does "mount and format data" mean? I can format data, system and cache but I don't see "mount" at all.
The Collective DL Fails
So I am trying to download the package that is for this which would be most helpful for me as I'm trying to help out my pastors wife with her Galaxy Tab, I started the download and it got all the way up to 144MB and quit, and file won't work.
Is there somewhere else that you can put it so we can try downloading from there? Can I give you my dropbox and you can drop it in there?
Again just to say I don't have a problem with HEIMDALL I have a problem downloading your link for the files needed for the flash.
I would really like to try to get this working for her as I've been looking around for a solution for this thing for about 2wks already and its been blowing my mind.
So we need the DL fixed so we can download the Collective Package.
Thanks again for the help and great write-up.
Lem
:angel:
chi_tilt said:
So I am trying to download the package that is for this which would be most helpful for me as .......
So we need the DL fixed so we can download the Collective Package.
Thanks again for the help and great write-up.
Lem
:angel:
Click to expand...
Click to collapse
Try a direct download link
http://www.theandroidcollective.org/i800/public/TheCollective-HelperPackage_sch-i800.zip
Sometimes download errors like yours seem to happen when the user is behind a proxy.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
No 3G with alroger's latest kernel
I guess this is a pretty common issue for CDMA user's. alroger's download page says to copy the modem.bin to the /radio. I downloaded the original verizon modem binaries for my sch-i800 but I don't see a /radio folder. In the about tablet section, baseband is unknown. I just created a radio folder on the root of the tablet and renamed my download modem.bin and stuck it in there. I'm about to reflash the just the kernel but I'm pretty sure that's not how it works. So how do I get my radio/modem back and get 3g working with this kernel? cafe-ti.blog.br/1956~cm10-1-sgt7-p1000.html
arielja87 said:
I guess this is a pretty common issue for CDMA user's. alroger's download page says to copy the modem.bin to the /radio. I downloaded the original verizon modem binaries for my sch-i800 but I don't see a /radio folder. In the about tablet section, baseband is unknown. I just created a radio folder on the root of the tablet and renamed my download modem.bin and stuck it in there. I'm about to reflash the just the kernel but I'm pretty sure that's not how it works. So how do I get my radio/modem back and get 3g working with this kernel? cafe-ti.blog.br/1956~cm10-1-sgt7-p1000.html
Click to expand...
Click to collapse
Easiest way is to tar the modem.bin and Odin it into the device.
Load it into the phone slot
Sent from my GT-P5110 using Tapatalk 4
Help to download...
Hi... I have tried many times to download the package (TheCollective-RootedStock-Odin-sch-i800.tar.md5) but I can not , the download starts fine, but not complete!.
If you could upload to another server like 4shared, mediafire, dropbox... I would be very grateful..
Still not working as it should
So I have downloaded the package finally and I Have done all the steps according to your writeup. Still doesn't give me a fresh startup on the tablet, I still get many error popups and also all my apps are still there.
What could I be doing wrong? Could there be something wrong with the tablet?
Any help on this would be great, as I'm dumbfounded on this already.
Thank You
Lem
Hello everyone! So after the new MediaTek DAA and SLA protection bypasses you can find GitHub repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX3085 (Realme 8) ONLY. DON'T DO ANY OF THESE IF YOU HAVE SOMETHING ELSE!
ALWAYS USE DOWNLOAD ONLY MODE OF SP FLASH TOOL.
DON'T TOUCH ANYTHING RELATED TO FORMAT ON SP FLASH TOOL! (IT'S WRITTEN EVERYWHERE, YOU WILL LOSE YOUR IMEIS IF YOU USE FORMAT ALL + DOWNLOAD. YOU ARE SAFE IF YOU USE DOWNLOAD ONLY.)
Requirements:
PC or Laptop
Internet connection
Realme 8
USB cable
Windows Method
Requirements:
Bypass Tools Pack - (DRIVER AND BYPASS FILES)
SP Flash Tool
Decrypted OFP (OPPO FIRMWARE PACKAGE) :
Indian
A.22 (Indian) - GDrive
A.24 (Indian) - GDrive
A.26 (Indian) - Gdrive
C.05 (Indian) - GDrive
C.09 (Indian) - GDrive
C.11 (Indian) - GDrive
Global
A.22 (Global) - GDrive
A.24 (Global) - GDrive
A.26 (Global) - GDrive
Install Python from Windows Store
libusb-win32 - Having Issues? Use this.
Get usbdk installer (.msi) from here and install it
Steps:
1) Extract the zip
2) Go to driver folder, find the .inf file right click and press install.
{
"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"
}
3) Download this file and install it, after installing power off phone and connect to pc while holding Vol+- (don't leave the buttons after connecting) . You might need this driver as well if it's not detected.
4) Press next, connect your device to PC while holding Vol+- buttons (your device needs to be powered off, and don't leave the buttons) and you will see the mtkdriver down below. Install it.
5) Choose MediaTek USB Port and install it.
6) Then run the brom.bat under Bypass folder.
7) Now power off the phone and connect the phone while holding volume + and - (Don't leave the buttons until the bypass is done)
8) After the above step Go into Flash Tool folder and open the SPFlash tool go to Options>Option
9) Click on Connections and select UART and set Baud Rate to 921600
10) After that choose scatter file and also if not set, set your download-agent. You don't need to select auth file as authorization is disabled. Once you do it, it should look like this. ALWAYS MAKE SURE DOWNLOAD ONLY MODE IS SELECTED! DON'T SELECT OTHER MODES!
Select all the Partitions except opporeserve2 and cdt_engineering. otherwise you will get errors.
*11) If you want to flash super.img partition also then download this scatter.txt file and replace it with the another scatter file which is present in the decrypted firmware folder. After that select it again in sp flash tool.
Again Make SURE "Download Only" is selected. Don't select ANYTHING ELSE! You will lose your IMEIs, Serial Numbers, Capability of Hardware Attestation etc. if you choose "Format data + Download" make SURE you selected "Download Only".
Now, you can start downloading with the button and after that a checkmark will appear. You can reboot your phone and use it like before now! All your userdata will (inevitably) be cleared!
After flashing it should look like this. Download has been complete. Enjoy!
"Congrats Now your Realme 8 is Unbricked "
Credits :
https://github.com/bkerler/ for decryptor and for creating the tool.
If you face any issues write them down below...
Some people having this problem so I want to add one more thing to the guide. If you are not having any issues related to boot then don't follow these steps.
After waiting more then 10 minutes, if it doesn't boot up/bootloop. Or shows DM-Verity corrupt error then do this.
1) Try boot into stock recovery by pressing volume up + power button after that when your screen flashes quickly unpress buttons.
2) Now press volume down + power button, by pressing these you will boot into stock recovery.
3) Go to format option and do a full format.
4) Your phone will definitely boot up after that.
Hi
I would like to ask how you obtained the system for realme 8 in the latest version.
Can you download somehow from your device?
HowWof said:
Hi
I would like to ask how you obtained the system for realme 8 in the latest version.
Can you download somehow from your device?
Click to expand...
Click to collapse
From realme offical site
Could you send a link because there is no information on the Polish realme site
HowWof said:
Could you send a link because there is no information on the Polish realme site
Click to expand...
Click to collapse
Realme 8 Firmware (RMX3085) - Realme Firmware
Realme 8 Firmware RMX3085 Official Flash File (Stock ROM). flash your phone using realme flashtool or MSM Download tool.
realmefirmware.com
if "Brick" occured in rooting process - then can recovery be done without data loss :
Prerequisite: firmware version on the body must the same as downloaded "Decrypted OFP" (as example both is A.22 )
HowTo:
at step of SPFlashing (currently that is 10-th)
- check ONLY next partitions in SPFlash to restore :
PRELOADER RECOVERY VBMETA LK LK2 BOOT
... and NO any of other
(as thats only are touched by currently described rooting processes)
after recovery exist on every boot:
"dm-verify corrupted..."
how to get out of this message?
Reset with clearing data not helps ...
DaLiV said:
after recovery exist on every boot:
"dm-verify corrupted..."
how to get out of this message?
Reset with clearing data not helps ...
Click to expand...
Click to collapse
Wait for 10mins if it didn't boot then.
Format with mtk client
python mtk e metadata,userdata,md_udc
that boots ... BUT
on every boot thet alerts about "corruption"
ok cleared partitions with python...
still the same alert ...
DaLiV said:
that boots ... BUT
on every boot thet alerts about "corruption"
ok cleared partitions with python...
still the same alert ...
Click to expand...
Click to collapse
Try booting into stock recovery and format from there
Ok. format from recovery menu solves ...
now that boots normally =
- no alert
-no boot allowing by pressing key required
good behaviour to see when boot subsystem altered, as at every boot alerted and required to press longer power button to confirm/allow starting ...
interesting, that is something new on mine (device versions) or overall ...
I have it anyway. have you solved it yet? Do I understand correctly?
after doing the insstruction, mine bootlooping and enters recovery mode
XCentrialG said:
after doing the insstruction, mine bootlooping and enters recovery mode
Click to expand...
Click to collapse
Maybe you missed some step. Can u explain ur problem briefly. What u did and what happened.
niki.rsb said:
I have it anyway. have you solved it yet? Do I understand correctly?
Click to expand...
Click to collapse
I Think that is not so solvable /possible if someone decode debug and finds /... but that is quite acceptable for rooting /if you don't want to make illegal spionage and so on/ ... also as if your device will be rooted by someone - you will see alert of changes on boot ... that is good ...
if you are rooted - you must be alerted .
but if you will going to stock rom and have protection - then flashing "stock" (surely without 3 partitions that IMEI-and-so-on-related ) and then format from recovery menu helps return to "factory" operation
Tony Stark said:
Maybe you missed some step. Can u explain ur problem briefly. What u did and what happened.
Click to expand...
Click to collapse
just a casual day to update my firmware, reboot and my phone refused to boot anymore, and then i came here, following all the steps very carefully (i read every steps twice so i dont make any mistake), and no luck.
XCentrialG said:
just a casual day to update my firmware, reboot and my phone refused to boot anymore, and then i came here, following all the steps very carefully (i read every steps twice so i dont make any mistake), and no luck.
Click to expand...
Click to collapse
There should be some mistake in your process. Because this guide is working and tested by many people.
Does global firmware have realme dialer instead of google dialer?
Can I flash Global firmware my indian device?
on your firmware package, it does not flashes super.img by default. Because in scatter file
- partition_index: SYS48
partition_name: super
file_name: super.img
is_download: false
changing false to true helps fixing destroyed super partition