I recently installed Android bootloader interface to make possible rooting of my phone. However, can I reverse somehow the process and remove the android logo and bootloader interface?
holocen said:
I recently installed Android bootloader interface to make possible rooting of my phone. However, can I reverse somehow the process and remove the android logo and bootloader interface?
Click to expand...
Click to collapse
Some more information would be useful (your device and guide you used etc).
I am also guessing you mean removing a custom bootloader? You can not remove the bootloader, unless you want a device that will not boot.
The bootloader works in much the same way as your computers BIOS and is not something that can be removed.
see: http://forum.xda-developers.com/showthread.php?t=1466228
"Bootloader:This small program's only job is to load other data and programs which are then executed from RAM.Often, multiple-stage boot loaders are used, during which several programs of increasing complexity load one after the other in a process of chain loading."
My device is ZTE Blade 3. I installed fastboot drivers and after that my ABI show up as green android logo. I made this video:
I used this drivers for fastboot:
Code:
http://www.filefactory.com/file/6et8eo31fq5v/n/fastboot_driver_B3_zip
These are files for rooting of my phone:
Code:
http://www.filefactory.com/file/35dokg7x0vkj/n/B3_root_NGT_zip
I installed modified Google USB driver - driver for fastboot, I guess? I successfully rooted and installed recovery coded for Blade 3. When I try to revert the original stock ROM of my phone, the only thing that is different is green android logo which boot shortly now but there was not before. That logo comes up after implementing fastboot drivers as in video above.
Anyone, please?
Sent from my ZTE BLADE III
Related
Pls help flashing boot.img for CM7 on Xperia Ray ("waiting for device"- error)
Hello,
I am desperately trying to get CM7 onto my Ray.
I got to the last point, but am severely stuck here
When I try to flash the boot img by <flashboot -i 0xfce flash boot boot.img>
it's always stuck at <waiting for device>
I already unlocked the phone using the test point method successfully and am Using the driver provided in the CM7 Wikia from the page about installing the android sdk and fastboot.
Can anyone help?
My OS is Win 7 Enterprise 64-bit
I believe that this should be in the General section, not the Development area.
While it's here though:
Whilst the phone is powered off, hold down Vol[+] as you insert the USB cable to your Ray, it should light up blue around the home button. If it doesn't you've not unlocked the bootloader properly.
If the blue light is there it would seem you've not got the correct drivers installed. Uninstall the ones currently in use and re-install.
The blue light shows up and I am certain the bootloader is unlocked as my log in S1Flash tool was 100% identical to that of the poster.
I tried several drivers to no avail, can you tell with one you used for your Ray or if you don't own a Ray which one I should use?
Thanks.
Also: Should the Phone show up ad Android ADB Interface in device manager?
Posted a reply in the proper thread, where you've also asked this question:
http://forum.xda-developers.com/showthread.php?t=1285977&page=4
Mycorrhiza said:
Hello,
I am desperately trying to get CM7 onto my Ray.
I got to the last point, but am severely stuck here
When I try to flash the boot img by <flashboot -i 0xfce flash boot boot.img>
it's always stuck at <waiting for device>
I already unlocked the phone using the test point method successfully and am Using the driver provided in the CM7 Wikia from the page about installing the android sdk and fastboot.
Can anyone help?
My OS is Win 7 Enterprise 64-bit
Click to expand...
Click to collapse
you must have a pure system there's none other AndroidPhone drivers.And install drivers from "flashtools" or other way.
Hi, I am trying to do some low level performance testing related to device processor cores through adb which I feel it is affected by Android background services and system stuff.
As I know that the Android boot sequence stages are as follow:
1.Execute Boot ROM code.
2.Execute the boot loader.
3.Load the Linux kernel.
4.Launch Zygote, which initializes the Dalvik VM.
5.System server which loads the Android system.
So my question is how can I interrupt this sequence to force it stop on stage 3 to load Linux kernel. This can help me implement my intermediary performance testings before loading again Android system.
Does Fastboot or Clockworkmod recovery can help here and load my device to a kind of Linux kernel?
Any hint will be appreciated.
Thanks.
mosed said:
Hi, I am trying to do some low level performance testing related to device processor cores through adb which I feel it is affected by Android background services and system stuff.
As I know that the Android boot sequence stages are as follow:
1.Execute Boot ROM code.
2.Execute the boot loader.
3.Load the Linux kernel.
4.Launch Zygote, which initializes the Dalvik VM.
5.System server which loads the Android system.
So my question is how can I interrupt this sequence to force it stop on stage 3 to load Linux kernel. This can help me implement my intermediary performance testings before loading again Android system.
Does Fastboot or Clockworkmod recovery can help here and load my device to a kind of Linux kernel?
Any hint will be appreciated.
Thanks.
Click to expand...
Click to collapse
I'm not 100% on the testing you are trying to do but what about installing Debian to your device, this would not use dalvik and be free from android all together?
Or remove Google services or whatever background stuff you feel may be messing with your tests?
You can use fastboot to force boot a kernel, if zimage and ramdisk are packed into an image then
fastboot boot nameofkernel.img
For more info on fastboot see here
http://forum.xda-developers.com/showthread.php?p=41374534
From my minimal testing and messing with bootloaders I can say it is possible to solder a UART connection to the logicboard and connect it to PC via a serial port (may need a device like an arduino as a bridge) where you can stop the bootloader in different sequences, this being you can trigger debugging modes that the bootloader has. This of course differs in each device but it is possible to enter a debug mode and shell terminal (not adb) before the bootloader finishes its process.
But in reality, depending on what your attempting you probably need a fully booted device so if your not interested in using a hex editor to force your bootloader to do what you want (which would probably take a lot of work) try fastboot to force boot whatever kernel you made or probably just flash Debian to your device
Sent from my Nexus 4 using Tapatalk 2
demkantor said:
I'm not 100% on the testing you are trying to do but what about installing Debian to your device, this would not use dalvik and be free from android all together?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I think the idea of installing Debian/Linux distro to the device is interesting so that I can get red of Dalvik.
But whenever I try to find a suitable Debian/Linux kernel to install on my device, I found that it will be installed on top of the current Android system ( same as Virtual machine). So Android and Dalvik are still there!
So where can I find a Debian/Linux kernel that will replace Android, not to set on top of it.
Thanks
How to modify bootloader to load kernel and ramdisk from SD Card?
demkantor said:
From my minimal testing and messing with bootloaders I can say it is possible to solder a UART connection to the logicboard and connect it to PC via a serial port (may need a device like an arduino as a bridge) where you can stop the bootloader in different sequences, this being you can trigger debugging modes that the bootloader has.
Click to expand...
Click to collapse
Can we modify bootloader to load kernel from some location other than eMMC? I'm talking in this context: https://forum.xda-developers.com/android/help/how-to-boot-sd-card-qmobile-z8-bricked-t3712171
I was upgrading the current Stock rom on my ZTE Nubia Z5s Mini, I went through the recovery mode to load the new rom and got a message saying that the rom installed correctly, I rebooted the device and now its stuck at the MIUI logo or if I try to load the recovery mode I get the Nubia logo just to load back to the miui logo again. I got the rom from the MIUI site its v5.
I've left the phone for over an hour hoping it was just loading up but no change, the phone heats up and even has a charger screen when plugged in.
Anyway to get back into the recovery mode to load the original rom again or any other way of fixing this? help :crying:
I've no idea how to help you with this but I'm bumping the thread because I know how you feel.
Sent from my HUAWEI Y536A1
I'm trying to flush the rom by using adb but with an issue, even thou my device is recognized as Nubia Z5s Mini in device manager it still gives a driver error "these have been installed" and in cmd adb it does not see the device.
Update : Got drivers for install from Clockwordmod website but it will only accept the drivers if I set the phone as a modem in device manager when installing them, still not recognized by adb using CMD.
Solved driver issue and qusb_download issue, ADB drivers are done through all drives in device manager pointing to the Google USB drivers and select adb interface then run CMD from within the Google SDK program folder in platform-tools to read the device.
Now using emmc but need to generate EMMCBLD.HEX & 7x30_msimage.mbn if anyone can help, I can enter adb using recovery mode but blocked from making changes in fastboot mode, currently in download mode which can see a drive H but need the two files to proceed any further.
Hey guys,
I am sorry if I am in the wrong place or am asking something wrong. This is my first time using these forums (and forums in general). If I need to be somewhere else kindly redirect me.
Anyway, I was with Verizon for a while but after some shady stuff I decided to break up with them. Beforehand I had bought outright a Sony Xperia Z2 Tablet. Because I did not want anything Verizon on it I decided to root it, and flash a good ROM onto it (Cyanogenmod was my idea, but at the time I don't think they supported it? I'm not good with ROMS). Anyway, the rooting was completely successful and I had a custom recovery (TWRP) installed. I was ready to flash the ROM. Unfortunately, I wasn't paying attention and grabbed the wrong ROM. What ended up happening is when I attempted to reboot after "flashing", the device didn't show anything on the screen and just kept vibrating. After some digging around I found it might be "soft-bricked". I had at one time found a guide that told me how to undo this by using SDK Tools and Fastboot Mode (blue LED), but cannot find the guide anymore.
I was wondering if ANYONE could help me undo this mistake, and get the tablet back to it's original state or with a nice compatible ROM. I am currently in Fastboot mode and it is plugged into my ASUS Laptop running Windows 7. Any and all help would be GREATLY appreciated. Thank you so much for taking time to read this.
EDIT: So a breakdown is I cannot interact with the tablet directly. There is absolutely no interface. Just a screen that won't turn on. Meaning if there is a method it can't be done on the tablet. The old guide I found was explaining how to do it through Windows while the tablet was plugged into it via USB.
Also the bootloader was never unlocked so I think that was also an issue.
First of all, if your bootloader is locked, you cannot install CM because you cannot change the Kernel. You can only use Sony-certified Kernels which won't work with CM. So Sony-based ROMs are your only options
But what you can do is:
- Go into fastboot mode (turn off your tablet, connect it to your PC and press volume up. If the blue LED shows up, you are in fastboot)
- With fastboot, you should be able to flash a ROM (preferably Android 4.4, so you can root again)
- Then root, install dual recovery
- Flash the correct ZIP
Alternative:
- Unlock Bootloader
- Flash recovery
- Flash CM
BabelHuber said:
First of all, if your bootloader is locked, you cannot install CM because you cannot change the Kernel. You can only use Sony-certified Kernels which won't work with CM. So Sony-based ROMs are your only options
But what you can do is:
- Go into fastboot mode (turn off your tablet, connect it to your PC and press volume up. If the blue LED shows up, you are in fastboot)
- With fastboot, you should be able to flash a ROM (preferably Android 4.4, so you can root again)
- Then root, install dual recovery
- Flash the correct ZIP
Alternative:
- Unlock Bootloader
- Flash recovery
- Flash CM
Click to expand...
Click to collapse
Can you simplify this? Where do I find the ROM (again, this was a tablet from Verizon so I assume on top of the Sony ROM I need the Verizon version of it?) And I understand I cannot install CM unless the bootloader is unlocked; do you know how to do this?
I'm confused by the first set of instructions as I cannot use the tablet directly. How will I flash the ROM (and which is the right ROM and where can I find it?) through the computer since the tablet can't be interacted with. There is absolutely no interface to interact with whatsoever. Which ROM do I download for the Verizon Sony Xperia Z2 Tablet and how do I flash it using Fastboot? I assume I do it thru my computer?
Sorry, but you'll have to Google a little bit - I haven't had your exact problem.
But as long as you can get into fastboot mode, nothing is lost.
There also is the Sony ftf tool or so, the Windows program name is Emma. This should be easier than using fastboot.
Also there is a sony site for bootloader unlocking. You can check whether your bootloader can be unlocked at all.
Hey Everybody!
I am new to this forum, looking for a way to root my trekstor Surftab breeze 9.6 Quad. I already tried out the recommended tools, unfortunately none of them worked out. Is anyone of you aware of a method rooting the tab? Or did anyone already rooted it?
First ofall I am looking for a way to move files and apps to the external sd and delete pre-installed apps. Farther, if possible and available, a custom rom would be pretty amazing.
I'm only familiar to nexus root toolkit on my old nexus 4, otherwise I'm a newbie in rooting.
Maybe there's some of you able to help me. If necessary, I will look up more information on the tablet.
Lucas
Maybe as an Update:
Trying to build a working adb connection using the andorid sdk tools, the surftab is not listed as a device in "adb devices"
Anyone out there who can help me with the tablet?
Alright, new update for today.
I was able to get a driver running and the root-toolkits like KingoRoot, KingRoot, One Click root etc. noticed the device, I even was able to start the rooting, but all of those tools said "Root failed" or "Your device is soild to root".
Looks like those one click solution aren't able to root the surftab. I also tried towelroot and framaroot, both without any success.
I am still looking for help
If you are still interested, I successfully dumped whole eMMC memory from this tablet, so I can send you, for example, the boot partition. You can try patch it with Magisk
The magic
Yes, if it's not difficult for you, you can share the firmware. I will be grateful
Hi!
I attached xz-compressed stock boot.img for you!
Also, I have full eMMC dump, but:
recovery partition data are not usable (overwritten by uncompatible recovery image during mine tests)
no data partition
no platform bootloader partitions mmc0boot0 and mmc0boot1
Trekstor-Surftab-Breeze-9.6-ST96416-1-emmc-dump.dd.xz [1.12 GB]
Decompress and use kpartx tool (need force to ignore omitted data partition)
I have this tablet rooted now, so you can ask me for anything about it.
With love for all open source,
petabeda
Just one thing: fastboot boot is not supported here, so If you are afraid, flash modified boot.img to recovery partition with fastboot flash recovery boot.img for test (adb reboot and then adb reboot recovery
You will lost your recovery, but, at least, no bricked device in case of error (recovery is actually second boot partition)
petabeda said:
Just one thing: fastboot boot is not supported here, so If you are afraid, flash modified boot.img to recovery partition with fastboot flash recovery boot.img for test (adb reboot and then adb reboot recovery
You will lost your recovery, but, at least, no bricked device in case of error (recovery is actually second boot partition)
Click to expand...
Click to collapse
I have two surftab tablets. One version of the SIM card is fully functional. Another wifi version will not load. When loading, the orange logo at the moment of "collection" freezes. If there is, you can go into recovery even factory reset.
But nothing changes. I believe that the EMMC resource has been exhausted and therefore this behavior.
and to be honest, I don’t know how to write the partition. Since only the adb sideload command is available in recovery mode. Apparently, it is impossible to overwrite the firmware except through the programmer.
Until that time, I could not even pull out the firmware. Since there was no root access
Thank you for your help. As a thank you, I will give you a link to a tool to repair the Nexus 7 bootloader. Through a vulnerability in the tegra cpu. As I understand it, I use this method to hack the nintendo switch. I personally bought 4 nexus 2012 on the secondary market and one of them was able to restore in this way. They of them had a damaged eMMC other power controller. And even with a soldering station, I could not replace it because there is no suitable frame for the reball. In general, nexus are not bad, but there is very little disk space for installing google services and GAPPS are useless. And it is difficult to change partition. And it makes no sense because of the available firmware.
I see, you can''t unlock bootloader, because your device is not bootable at all. So, there is no way to get into fastboot mode?
We are anti e-waste fighters giving second chances!
The first photo is the available recovery menu. Where after choosing a factory reset, nothing changes. And through the adb update, only sideload mode is available.
The factory partition is not corrupted as the restore completes successfully. But the download fails. And not just does not occur, but freezes as in the screenshot above. Most likely a hardware problem eMMC.
Earlier, I saw something similar, for example, in Asus Zenpad, if turn off or connect the camera incorrectly, then the download stops. But here animation is stuck.
I don't know how to check eMMC exactly.
logs files is empty
And with recovery, no commands are available (like adb or fasboot)
There is a one way how to diagnose/repair/have fun with that Trekstor tablet - If you could and want to disassemble it:
have your tablet powered off
disassemble the tablet
carefully disconnect FFC cables (display and digitizer)
remove mainboard screws
at back side in the center of the board, there are three testpoints.......yes you are thinking right, these are actually 1.8V UART signals and GND
Connect these signals to your serial converter (in my case, Raspberry Pi), be careful and talk with the same loundnesses
Don''t power on the tablet, only plug usb cable, tablet will try boot and run healthd (charging mode with battery animation)
Your console will show you the magic (PBL/SBL) bootloader messages and Linux log and event, maybe, the console (though no root), lalalal (/dev/ttyFIQ0)
Wish you luck
After that, if everything goes well, you should be able to use reboot fastboot command to get fastboot mode !